From: Timothy Miller <miller@techsource.com>
To: Robert Love <rml@ximian.com>
Cc: Marcus Hartig <m.f.h@web.de>, linux-kernel@vger.kernel.org
Subject: Re: status of Preemptible Kernel 2.6.7
Date: Wed, 23 Jun 2004 15:30:18 -0400 [thread overview]
Message-ID: <40D9DA4A.3070700@techsource.com> (raw)
In-Reply-To: <1088017171.14159.2.camel@betsy>
Robert Love wrote:
> On Wed, 2004-06-23 at 13:57 -0400, Timothy Miller wrote:
>
>
>>I vaguely recall someone recently talking about eliminating preempt by
>>improving low-latency. See, if everything were ideal, we wouldn't need
>>preempt, because all drivers would yield the CPU at appropriate times.
>
>
> If everything held locks for only sane periods of time, we would not
> need gross explicit yielding all over the place.
>
> To answer Marcus's question: go for it and use it.
I wasn't talking about locks. I was talking about kernel functions
taking long periods of time, cases where preempt has been useful to
reduce kernel latency.
Holding locks for extended periods is something else entirely.
I presume there are sane cases where a kernel function will need to
execute for a "long time", like when doing PIO disk access or COW, etc.
It would be good to have a way to limit the impact of those functions
in terms of user-perceived latency, just as preempt has done, but
without preempt.
At least, I thought that was the idea.
Now, the thing is, if you have explicit cooperative yields, then a slow
CPU might not yield often enough, and a fast CPU would yield too often.
Preempt has the advantage of using real time so that CPUs can
maximize throughput without affecting latency.
next prev parent reply other threads:[~2004-06-23 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 16:38 status of Preemptible Kernel 2.6.7 Marcus Hartig
2004-06-23 17:57 ` Timothy Miller
2004-06-23 18:59 ` Robert Love
2004-06-23 19:30 ` Timothy Miller [this message]
2004-06-23 19:23 ` Robert Love
2004-06-23 19:58 ` Timothy Miller
2004-06-24 13:12 ` Marcus Hartig
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=40D9DA4A.3070700@techsource.com \
--to=miller@techsource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.f.h@web.de \
--cc=rml@ximian.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.