All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrea Arcangeli <andrea@novell.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Robert Love <rml@novell.com>, Roland Dreier <roland@topspin.com>,
	linux-kernel <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 00:16:46 -0400	[thread overview]
Message-ID: <1097036205.1359.19.camel@krustophenia.net> (raw)
In-Reply-To: <41636FCF.3060600@pobox.com>

On Wed, 2004-10-06 at 00:08, Jeff Garzik wrote:
> Preempt will always be something I ask people to turn off when reporting 
> driver bugs; it just adds too much complicated mess for zero gain.

I agree that many people are using preempt who should not be.  Currently
the Kconfig help recommends enabling preempt for a "desktop or embedded
system".  Maybe we should lose the desktop part.  99% of users do not
need the low latencies that require preempt, and those users know who
they are.

Lee


  reply	other threads:[~2004-10-06  4:16 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
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 [this message]
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=1097036205.1359.19.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=andrea@novell.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rml@novell.com \
    --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.