From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org, davej@redhat.com,
Andrew Morton <akpm@osdl.org>
Subject: Re: remove cpu hotplug bustification in cpufreq.
Date: Sun, 23 Jul 2006 06:09:14 +0200 [thread overview]
Message-ID: <1153627754.7359.17.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607221813020.29649@g5.osdl.org>
On Sat, 2006-07-22 at 18:15 -0700, Linus Torvalds wrote:
>
> On Sat, 22 Jul 2006, Andrew Morton wrote:
> >
> > It was just wrong in conception. We should not and probably cannot fix it.
> > Let's just delete it all, then implement version 2.
>
> Well, I just got Ashok's trial patches which turns the thing into a rwsem
> as I outlined earlier.
with rwsems being 100% fair... how is that going to make a difference?
Other than just making the deadlock harder to trigger because the writer
needs to come in just at the right time...
next prev parent reply other threads:[~2006-07-23 4:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 19:40 Dave Jones
2006-07-23 0:10 ` Linus Torvalds
2006-07-23 1:06 ` Andrew Morton
2006-07-23 1:15 ` Linus Torvalds
2006-07-23 4:09 ` Arjan van de Ven [this message]
2006-07-23 17:20 ` Linus Torvalds
2006-07-23 18:12 ` Linus Torvalds
2006-07-23 18:34 ` Patrick McFarland
2006-07-24 10:52 ` Arjan van de Ven
2006-07-23 5:34 ` Andrew Morton
2006-07-23 8:29 ` Arjan van de Ven
2006-07-23 16:24 ` Ingo Molnar
2006-07-25 0:21 Chuck Ebbert
2006-07-25 0:59 ` Linus Torvalds
2006-07-25 15:06 ` Erik Mouw
2006-07-25 18:54 ` Ingo Molnar
2006-07-25 19:30 ` Arjan van de Ven
2006-07-25 20:57 ` Linus Torvalds
2006-07-25 20:46 ` Dave Jones
2006-07-25 20:59 ` Linus Torvalds
2006-07-26 17:12 ` Russell King
2006-07-26 17:53 ` Dave Jones
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=1153627754.7359.17.camel@laptopd505.fenrus.org \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®