From: Josh Green <jgreen@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Noticeable latency problems after upgrade from 2.4.3 to 2.4.4
Date: Fri, 18 May 2001 19:41:50 -0700 [thread overview]
Message-ID: <3B05DD6E.15320298@users.sourceforge.net> (raw)
I'm experiencing nasty latency problems (stalls X cursor, Maelstrom
arcade game :), etc) with Linux kernel 2.4.4. I did not have this
problem with 2.4.3. I have Mandrake 8.0. I made sure that I compiled the
2.4.4 kernel with the older egcs 1.1.2 (although I did try it with the
controversial gcc 2.96 with the same results).
Both kernels were downloaded off of kernel.org (not Mandrake modified)
and I used the same .config.
Heres a description of my system:
I'm using reiserfs
Linux version 2.4.4 (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2
release / Linux-Mandrake 8.0))
XFree86 4.0.3
CPU: AMD K6 550 MHZ
Memory: 128 MB
HD: WDC WD300BB-00AUA1, ATA IDE DISK drive
Chipset: VIA VT82C586
Both kernels had the following hard disk tuning parameters (excerpt from
hdparm):
/dev/hda:
multcount = 0 (off)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
I even set the multcount to 8 with a slight increase in hdparm -t read
performance, but still bad latency.
The latency issues mainly occur with compiling programs. Compiling my
autoconf based program and running Maelstrom at the same time served as
a crude test. 2.4.4 would have large skip outs in sound and pauses in
gameplay, whereas 2.4.3 runs very smooth. I also did an hdparm -t while
running tests, I did not perceive the problem in this case though,
suggesting something besides hard disk access.
If anyone has any info on what could be causing this, please let me
know. CC me as I'm not on the list. If there isn't any knowledge of this
problem, I will try to track it down myself. I guess perhaps narrowing
it down to a particular pre version and maybe doing some kernel
profiling (I have no idea how) if all else fails. Lates..
Josh Green
reply other threads:[~2001-05-19 2:44 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=3B05DD6E.15320298@users.sourceforge.net \
--to=jgreen@users.sourceforge.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