From: Robert Love <rml@ximian.com>
To: Timothy Miller <miller@techsource.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:23:31 -0400 [thread overview]
Message-ID: <1088018611.14161.5.camel@betsy> (raw)
In-Reply-To: <40D9DA4A.3070700@techsource.com>
On Wed, 2004-06-23 at 15:30 -0400, Timothy Miller wrote:
> 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 know what you were talking about. I was replying that it seems better
overall to me if we work to eliminate long lock hold times (which then
eliminates long non-preemption times) than litter the kernel with
explicit rescheduling statements.
Robert Love
next prev parent reply other threads:[~2004-06-23 19:23 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
2004-06-23 19:23 ` Robert Love [this message]
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=1088018611.14161.5.camel@betsy \
--to=rml@ximian.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.f.h@web.de \
--cc=miller@techsource.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.