All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Andrew Morton <akpm@zip.com.au>,
	Bob McElrath <mcelrath+linux@draal.physics.wisc.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: low-latency patches
Date: 06 Oct 2001 18:22:09 -0400	[thread overview]
Message-ID: <1002406931.1911.6.camel@phantasy> (raw)
In-Reply-To: <20011006150024.C2625@mikef-linux.matchmail.com>
In-Reply-To: <20011006010519.A749@draal.physics.wisc.edu> <3BBEA8CF.D2A4BAA8@zip.com.au>  <20011006150024.C2625@mikef-linux.matchmail.com>

On Sat, 2001-10-06 at 18:00, Mike Fedyk wrote:
> And exactly how is low latency going to hurt the majority?

The problem is people argue that a preemptible kernel lowers throughput
since I/O is now interrupted.  Of course, if they fear that, maybe we
should switch to cooperative multitasking!

Anyhow, tests show the preemptible kernel has a negligible effect on
throughput -- in fact in some cases we improve it since overtime we
better distribute system load.  This is one reason why I ask for dbench
or bonnie benchmarks from the preemption users.  Results are good.

The other concern is that added complexity is a Bad Thing, and I agree,
but the complexity of preemption is insanely low.  In fact, since we use
so many preexisting constructs (such as SMP locks), its practically
nothing.

> This reminds me of when 4GB on ia32 was enough, or 16 bit UIDs, or...
>
> Should those have been left out too just because the people who needed them
> were few?

Agreed.

> If the requirements for manufacturing control, or audio processing, or etc
> will make my home box, or my server work better then why not include it?

That is my thought process, too.

	Robert Love


  reply	other threads:[~2001-10-06 22:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06  6:05 low-latency patches Bob McElrath
2001-10-06  6:46 ` Andrew Morton
2001-10-06 16:33   ` Daniel Phillips
2001-10-06 20:42   ` Bob McElrath
2001-10-06 22:00   ` Mike Fedyk
2001-10-06 22:22     ` Robert Love [this message]
2001-10-08 12:47     ` Helge Hafting
2001-10-08 17:41       ` george anzinger
2001-10-08 18:24         ` Andrew Morton
2001-10-08 18:36           ` Alan Cox
2001-10-07  1:12   ` Robert Love
2001-10-07  2:38     ` Jeffrey W. Baker
2001-10-07  2:55       ` Robert Love
2001-10-06 22:36 ` Robert Love
2001-10-06 22:46   ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10 15:27 David Balazic
2001-03-08 13:06 Andrew Morton

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=1002406931.1911.6.camel@phantasy \
    --to=rml@tech9.net \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcelrath+linux@draal.physics.wisc.edu \
    --cc=mfedyk@matchmail.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.