[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080511130226.GR19219@parisc-linux.org>
Date: Sun, 11 May 2008 07:02:27 -0600
From: Matthew Wilcox <matthew@....cx>
To: Ingo Molnar <mingo@...e.hu>
Cc: Sven Wegener <sven.wegener@...aler.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Andi Kleen <andi@...stfloor.org>,
LKML <linux-kernel@...r.kernel.org>,
Alexander Viro <viro@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git pull] scheduler fixes
On Sun, May 11, 2008 at 02:52:16PM +0200, Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
>
> > > So I deem my fix "proven by thought experiment". I haven't tried
> > > booting it or anything.
> >
> > i actually have two fixes, made earlier today. The 'fix3' one has been
> > confirmed by Sven to fix the regression - but i think we need the 'fix
> > #2' one below as well to make it complete.
>
> i just combined them into a single fix, see below.
That's mangled ... why did you move __up around?
> list_del(&waiter.list);
> + if (unlikely(!list_empty(&sem->wait_list)) && sem->count)
> + __up(sem);
That's an unnecessary wakeup compared to my patch.
> return ret;
> }
>
> @@ -254,9 +264,10 @@ static noinline int __sched __down_timeo
> return __down_common(sem, TASK_UNINTERRUPTIBLE, jiffies);
> }
>
> -static noinline void __sched __up(struct semaphore *sem)
> -{
> - struct semaphore_waiter *waiter = list_first_entry(&sem->wait_list,
> - struct semaphore_waiter, list);
> - wake_up_process(waiter->task);
> -}
> +
> + /*
> + * Rotate sleepers - to make sure all of them get woken in case
> + * of parallel up()s:
> + */
> + list_move_tail(&waiter->list, &sem->wait_list);
Seems like extra cache line dirtying for no real gain over my solution.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists