From: Ingo Molnar <mingo@elte.hu>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] De-macro spin_trylock_irq, spin_trylock_irqsave, write_trylock_irqsave
Date: Sun, 17 Aug 2008 11:31:15 +0200 [thread overview]
Message-ID: <20080817093114.GA21303@elte.hu> (raw)
In-Reply-To: <87pro8psk1.fsf@skyscraper.fehenstaub.lan>
* Johannes Weiner <hannes@saeurebad.de> wrote:
> >> (but it would also be hugely invasive, with not much upside with
> >> tons of downside like years of migration fallout and having to
> >> rewrite hundreds of kernel hacking books ;-) )
> >
> > I want my money back for scheduler chapter from "Understanding the
> > Linux Kernel"!
>
> I agree that this argument of Ingo's is not a very good one... ;)
i see the smiley, but still - there's a huge difference between the
"pain" caused by a much better scheduler [ hey, did you expect me to say
anything else? ;-) ] and a rather arbitrary value->pointer parametering
change to a core API that is used _everywhere_.
Ingo
next prev parent reply other threads:[~2008-08-17 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 9:59 [PATCH] De-macro spin_trylock_irq, spin_trylock_irqsave, write_trylock_irqsave Alexey Dobriyan
2008-08-16 13:31 ` Jiri Slaby
2008-08-16 20:48 ` Alexey Dobriyan
2008-08-16 21:21 ` Linus Torvalds
2008-08-17 7:52 ` David Miller
2008-08-16 13:46 ` Ingo Molnar
2008-08-16 21:04 ` Alexey Dobriyan
2008-08-16 21:18 ` Johannes Weiner
2008-08-17 9:31 ` Ingo Molnar [this message]
2008-08-17 12:30 ` Johannes Weiner
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=20080817093114.GA21303@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=hannes@saeurebad.de \
--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