From: John Levon <movement@marcelothewonderpenguin.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][RFC][PATCH][CLEANUP] task->state cleanup: pilot
Date: Sun, 7 Apr 2002 12:00:10 +0100 [thread overview]
Message-ID: <20020407110010.GA11680@compsoc.man.ac.uk> (raw)
In-Reply-To: <20020406220612.GF839@stingr.net> <1018136462.899.119.camel@phantasy>
On Sat, Apr 06, 2002 at 06:41:01PM -0500, Robert Love wrote:
> If anyone can verify where it is safe in this code to use
> __set_current_state instead, speak up so Paul can make the micro
> optimization accordingly.
Ugh, please don't. There is enough mystery as to which one is safe to
use when already.
Is there really a circumstance where avoiding the mb makes a noticable
difference (in driver code, core code is something else ...) ?
john
--
"I never understood what's so hard about picking a unique
first and last name - and not going beyond the 6 character limit."
- Toon Moene
prev parent reply other threads:[~2002-04-07 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 22:06 [CFT][RFC][PATCH][CLEANUP] task->state cleanup: pilot Paul P Komkoff Jr
2002-04-06 23:41 ` Robert Love
2002-04-07 11:00 ` John Levon [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=20020407110010.GA11680@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--cc=linux-kernel@vger.kernel.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