From: Robert Love <rml@tech9.net>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@transmeta.com, hch@caldera.com, arjanv@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preempt abstraction
Date: 08 Jan 2002 13:57:28 -0500 [thread overview]
Message-ID: <1010516250.3229.21.camel@phantasy> (raw)
In-Reply-To: <10940.1010511619@warthog.cambridge.redhat.com>
In-Reply-To: <10940.1010511619@warthog.cambridge.redhat.com>
On Tue, 2002-01-08 at 12:40, David Howells wrote:
>
> The following patch abstracts access to need_resched:
>
> ftp://infradead.org/pub/people/dwh/preempt-252p10.diff.bz2
>
> It replaces most C-source read accesses to it with need_preempt() which
> returns true if rescheduling is necessary.
Nice patch!
A couple of points:
Why not use the more commonly named conditional_schedule instead of
preempt() ? In addition to being more in-use (low-latency, lock-break,
and Andrea's aa patch all use it) I think it better conveys its meaning,
which is a schedule() but only conditionally.
I'm sure it is just being pedantic, but why not just make need_preempt
and preempt (which I would rename need_schedule and
conditional_schedule, personally) defines? Example:
#define need_schedule() (unlikely(current->need_resched))
#define conditional_schedule() do { \
if (need_schedule()) \
schedule(); \
} while(0);
Next, in kernel/sched.c you wrap need_preempt in an unlikey() but note
it is unlikely by design ... Same in mm/vmscan.c a couple times.
Oh, and the patch is confusingly similar to preempt-kernel in name, but
I guess that is my problem. :-)
Anyhow, I like. 2.5 _and_ 2.4?
Robert Love
next prev parent reply other threads:[~2002-01-08 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 17:40 [PATCH] preempt abstraction David Howells
2002-01-08 18:13 ` Jeff Garzik
2002-01-08 18:57 ` Robert Love [this message]
2002-01-08 18:59 ` Christoph Hellwig
2002-01-08 20:52 ` Andrew Morton
2002-01-08 21:25 ` Roger Larsson
2002-01-08 22:12 ` Daniel Phillips
2002-01-08 22:35 ` David Howells
2002-01-08 22:46 ` David Howells
2002-01-08 23:05 ` Robert Love
2002-01-08 21:30 ` Robert Love
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=1010516250.3229.21.camel@phantasy \
--to=rml@tech9.net \
--cc=arjanv@redhat.com \
--cc=dhowells@redhat.com \
--cc=hch@caldera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.