From: Robert Love <rml@tech9.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, kpreempt-tech@lists.sourceforge.net
Subject: Re: [PATCH] 2.5: conditional schedules with a preemptive kernel
Date: 21 Feb 2002 15:35:41 -0500 [thread overview]
Message-ID: <1014323742.2576.41.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0202211227260.18900-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0202211227260.18900-100000@penguin.transmeta.com>
On Thu, 2002-02-21 at 15:29, Linus Torvalds wrote:
>
> On 20 Feb 2002, Robert Love wrote:
> >
> > With a preemptive kernel, explicit conditional schedules when
> > preempt_count is zero are a waste of cycles and code size.
>
> Hmm.. Are there any other kind?
>
> Another way of saying this: how can a conditional schedule _ever_ be
> nothing but a waste of cycles and code size with preemption enabled?
>
> If the reason is the BKL, then I would much prefer those paths to be
> BKL-fixed, than have two different conditional schedules.
>
> In short, I'd rather get a patch that just unconditionally makes the
> conditional schedules no-ops with preemption enabled. That would seem to
> make a lot more sense.
I assume (and hope) the reason is always the BKL.
I would rather not eliminate any explicit reschedules from the kernel
for the preemptive kernel case only. That sort of defeats a purpose
(response improvement) of the kernel.
And I wholeheartedly agree that the situations where the BKL is held
should be handled and an ideal solution is to just not explicitly
schedule anywhere in the kernel with a preemptive kernel. But I suspect
this will involve a lot of dark magic wrt BKL locking semantics.
What do you have in mind?
Robert Love
prev parent reply other threads:[~2002-02-21 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 1:26 [PATCH] 2.5: conditional schedules with a preemptive kernel Robert Love
2002-02-21 20:29 ` Linus Torvalds
2002-02-21 20:35 ` Robert Love [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=1014323742.2576.41.camel@phantasy \
--to=rml@tech9.net \
--cc=kpreempt-tech@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox