mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
Cc: linux-audio-dev@music.columbia.edu, linux-kernel@vger.kernel.org
Subject: Re: [linux-audio-dev] latency performance of 2.4 and 2.5...
Date: Mon, 14 Oct 2002 01:36:16 -0700	[thread overview]
Message-ID: <3DAA8200.2AF20C5C@digeo.com> (raw)
In-Reply-To: <3DAA7E8F.36B03682@folkwang-hochschule.de>

Joern Nettingsmeier wrote:
> 
> some new interesting results with 2.5.42:
> 
> http://spunk.dnsalias.org/latencytest/2.5.42/2x256.html
> 
> overall much worse, *but* greatly reduced latency peaks (max. 6 ms) as
> compared to 2.5.41:
> 
> http://spunk.dnsalias.org/latencytest/2.5.41/2x256.html
> 
> here the peaks easily reach 13 ms.

Rather depends on the filesystem.  ext3 does its own write scheduling,
and does stuff inside lock_kernel().  It needs a couple of scheduling
points I guess.

I'd expect ext2 to work OK with preemption, but nobody has really
looked yet.  Unless you're using ftruncate() (grr.)

> i'm not really sure what to make of this....
> can someone explain ?
> 
> andrew, it seems part of your mm patch was merged - is there an updated
> patch around that will add the missing hunks ?

Well 2.5.41 had the big change to the truncate code, which was
a rather important part of this whole effort.  I can't immediately
think of a 2.5.42 change which would do this...

But nobody has really got down and dug out the toolkit on
2.5 scheduling latency.  I guess I should do that soon.

  reply	other threads:[~2002-10-14  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-11 12:48 Joern Nettingsmeier
2002-10-14  8:21 ` [linux-audio-dev] " Joern Nettingsmeier
2002-10-14  8:36   ` Andrew Morton [this message]
2002-10-14  8:52     ` Joern Nettingsmeier
2002-10-14 12:20       ` Mark Knecht

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=3DAA8200.2AF20C5C@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-audio-dev@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nettings@folkwang-hochschule.de \
    /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

all inboxes | Powered by JetHome®