From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Roland Dreier <roland@topspin.com>, linux-kernel@vger.kernel.org
Subject: Re: Preempt? (was Re: Cannot enable DMA on SATA drive (SCSI-libsata, VIA SATA))
Date: Wed, 06 Oct 2004 11:28:20 +1000 [thread overview]
Message-ID: <41634A34.20500@yahoo.com.au> (raw)
In-Reply-To: <4163465F.6070309@pobox.com>
Jeff Garzik wrote:
> Roland Dreier wrote:
>
>> Jeff> I strongly recommend disabling kernel preemption. It is a
>> Jeff> hack that hides bugs.
>>
>> Why do you say that? Preempt seems to be the cleanest way to low
>> latency, and if anything it exposes locking bugs and races rather than
>> hiding anything.
>
>
> Clean? Hardly. It breaks up code paths that were never written to be
> broken up.
But lots of things change. Unserialising the kernel broke code paths.
> The proper fix is to locate and fix high latency code paths.
> Preempt does nothing but hide those high latency code paths, and
> discourage people from seeking a better solution.
>
> Fix the drivers, rather than bandaid over them with preempt.
>
> If all code paths in the kernel were low latency, then you would not
> need preempt at all.
>
When you say low latency, you mean small lock hold times, *and*
cond_rescheds placed everywhere - it is this second requirement
that isn't the cleanest way of doign things.
With preempt, sure you still need small lock hold times. No big
deal.
next prev parent reply other threads:[~2004-10-06 1:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4136E7EF00073144@mail-3.tiscali.it>
2004-10-06 0:30 ` Cannot enable DMA on SATA drive (SCSI-libsata, VIA SATA) Gianluca Cecchi
2004-10-06 0:54 ` Jeff Garzik
2004-10-06 1:00 ` Preempt? (was Re: Cannot enable DMA on SATA drive (SCSI-libsata, VIA SATA)) Roland Dreier
2004-10-06 1:11 ` Jeff Garzik
2004-10-06 1:28 ` Nick Piggin [this message]
2004-10-06 1:32 ` Nick Piggin
2004-10-06 1:40 ` Jeff Garzik
2004-10-06 1:52 ` Robert Love
2004-10-06 1:55 ` Jeff Garzik
2004-10-06 2:02 ` Nick Piggin
2004-10-06 2:07 ` Jeff Garzik
2004-10-06 2:28 ` Nick Piggin
2004-10-06 3:17 ` Andrea Arcangeli
2004-10-06 3:27 ` Jeff Garzik
2004-10-06 3:43 ` Nick Piggin
2004-10-06 3:59 ` Jeff Garzik
2004-10-06 4:05 ` Lee Revell
2004-10-06 4:22 ` Nick Piggin
2004-10-06 15:16 ` Aleksandar Milivojevic
2004-10-06 4:03 ` Andrea Arcangeli
2004-10-06 4:08 ` Jeff Garzik
2004-10-06 4:16 ` Lee Revell
2004-10-06 4:26 ` Nick Piggin
2004-10-06 4:46 ` Andrew Morton
2004-10-06 6:04 ` Jeff Garzik
2004-10-06 6:16 ` Andrew Morton
2004-10-06 13:38 ` Jeff Sipek
2004-10-06 4:12 ` Lee Revell
2004-10-06 3:34 ` Nick Piggin
2004-10-06 2:07 ` Robert Love
2004-10-06 2:30 ` Nick Piggin
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=41634A34.20500@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.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.