public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Preemption patch, some more feedback
Date: 10 Sep 2001 17:26:08 -0400	[thread overview]
Message-ID: <1000157173.18895.24.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.30.0109101132410.4681-100000@toy.mandrakesoft.com>
In-Reply-To: <Pine.LNX.4.30.0109101132410.4681-100000@toy.mandrakesoft.com>

On Mon, 2001-09-10 at 11:41, Francis Galiegue wrote:
> Machine is Athlon 650, AMD Viper chipset, 256 MB RAM. Kernel is
> 2.4.9-ac10 + preempt patch + irc_conntrack patch from iptables.
> 
> The preempt patch largely improves multimedia latency (no surprise on
> that), I can watch a DivX smoothly (with mplayer, gfx being Matrox G400)
> and compile various stuff behind.
> 
> However, a very simple command destroys this completely:
> 
> cat /dev/zero >/dev/null
> 
> DivX playback then becomes sluggish, no visible difference in this case
> between stock kernel and "preempt" kernel.

A long-term lock must be held for the duration of `cat /dev/zero >
/dev/null' -- i dont know if it is in the access to /dev/null or
/dev/zero or in the basic file operation itself.

as long as a lock is held, preemption can not occur.

what do we do? for the short term, and the benefit of everyone (UP, SMP,
and preemption users) we need to eliminate long-held locks with a better
solution.

in the long term, we can look at having the preemption patch use various
different types of locks (priority locks, spin then sleep locks, etc.)

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


           reply	other threads:[~2001-09-10 21:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.30.0109101132410.4681-100000@toy.mandrakesoft.com>]

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=1000157173.18895.24.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox