From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Con Kolivas <kernel@kolivas.org>,
ck@vds.kolivas.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [ck] Re: [PATCH] -mm: Small schedule() optimization
Date: Fri, 17 Mar 2006 10:52:08 +0100 [thread overview]
Message-ID: <20060317095208.GA31745@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060317091347.GD13387@elte.hu>
Hi,
On Fri, Mar 17, 2006 at 10:13:47AM +0100, Ingo Molnar wrote:
>
> * Con Kolivas <kernel@kolivas.org> wrote:
> > Probably better to just
> > if (unlikely(in_atomic())) {
> > if (!current->exit_state) {
> >
> > Ingo?
>
> yeah. There's not much point in nesting likely/unlikely. In fact we can
> just merge the two conditions, as per updated patch below.
ACK, thanks!
> Ingo
Andreas Mohr
prev parent reply other threads:[~2006-03-17 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 17:54 Andreas Mohr
2006-03-11 1:00 ` Con Kolivas
2006-03-17 9:13 ` Ingo Molnar
2006-03-17 9:52 ` Andreas Mohr [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=20060317095208.GA31745@rhlx01.fht-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®