public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Pang <ozone@algorithm.com.au>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@zip.com.au>, Robert Love <rml@tech9.net>
Subject: massive sched latency (even with akpm and rml's patches)
Date: Sat, 15 Sep 2001 20:23:14 +1000	[thread overview]
Message-ID: <1000549394.284238.2074.nullmailer@bozar.algorithm.com.au> (raw)

hello,

i'm getting (regular) latencies of up to 30ms on various
kernels, even with Andrew Morton low-latency patches and Nigel
Gamble/Robert Love's kernel pre-emption patches.

i'm running a Toshiba Satellite Pro 4280XDVD laptop, with 256MB
of RAM, and an IBM TravelStar 20GB hard disk.  the hard disk has
been 'tuned' (hdparm -m16 -c1 -u1 -d1 -k1 -S10 -X66), and for
akpm's patch, cat /proc/sys/kernel/lowlatency shows 1.  i'm
using Benno Senoner's latencytest progam, and i've tried using
the binary straight out of his .tar.gz archive as well as
compiling my own.  i've unloaded the pcmcia, usb and apm modules
on some of the tests as well, since i thought they might be
causing additional latency.  i'm using the ALSA snd-card-ymfpci
driver for sound output.  reiserfs is being used for the
partition which the latencytest is running on.

latencytest results are at

    http://www.algorithm.com.au/hacking/linux-lowlatency

kernels marked with 'll' have Andrew Morton's lowlatency patches
applied, and kernels marked with 'pe' have the patches from the
Linux Kernel Preemption Project applied.

any hints?  i've got about 500k left on my / partition thanks to
massive amount of kernel modules and kernels i've got installed
:).  i'm willing to do some hacking to the source, but i'm not
sure where to start tracking down the problem at the moment. 
thanks in advance!


-- 
#ozone/algorithm <ozone@algorithm.com.au>          - trust.in.love.to.save

                 reply	other threads:[~2001-09-15 10:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1000549394.284238.2074.nullmailer@bozar.algorithm.com.au \
    --to=ozone@algorithm.com.au \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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