From: Ingo Molnar <mingo@elte.hu>
To: Anton Blanchard <anton@samba.org>
Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] possible scheduler deadlock in 2.6.16
Date: Wed, 22 Mar 2006 14:16:46 +0100 [thread overview]
Message-ID: <20060322131646.GB11714@elte.hu> (raw)
In-Reply-To: <20060322104143.GC30422@krispykreme>
* Anton Blanchard <anton@samba.org> wrote:
> One way to solve this is to always take runqueues in cpu id order. To
> do this we add a cpu variable to the runqueue and check it in the
> double runqueue locking functions.
>
> Thoughts?
it's fine with me - the overhead to double_rq_lock() is minimal, and
it's not critical code either.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
prev parent reply other threads:[~2006-03-22 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 10:41 [PATCH] possible scheduler deadlock in 2.6.16 Anton Blanchard
2006-03-22 11:09 ` Nick Piggin
2006-03-22 12:17 ` Anton Blanchard
2006-03-22 22:52 ` Peter Williams
2006-03-22 13:16 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060322131646.GB11714@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).