From: DervishD <lkml@dervishd.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: usb-storage nice value
Date: Thu, 17 May 2007 12:03:08 +0200 [thread overview]
Message-ID: <20070517100308.GA14667@DervishD> (raw)
Hi all :)
I'm using kernel 2.6.19.5.
I'm having problems when reading/writing to external USB harddisks:
my *internal* harddisk stalls from time to time, so watching a movie
while copying data is a PITA (well, if the movie is bad, the leaps help
a bit...).
I thought about lowering the nice value of usb-storage (currently
it's -5), but if USB disks are not involved, the "leaps" in movies or
audio still happen when writing large amounts of data. I've tested with
different internal disks, and it doesn't happen with latest 2.4.x (at
least, it doesn't happen so annoyingly, leaps seldom happen, while with
2.6.x it's continuous).
My system is a bit modest: a 7 years old motheboard with VIA686B, a
1900+ Athlon XP, but with plenty of RAM (1280MB + 1GB swap). I know, if
I want more hard disk performance I should buy a new box with SATA or
whatever, but the fact is that I hadn't problems with the same hardware
and kernel 2.4.x. I need 2.6.x, so I cannot go back to 2.4.x.
Since messing with the nice values of kernel threads doesn't look
right to me, is there any way of modifying the pdflush behaviour so
large buffered writes are less "agressive" and doesn't block apps which
are just reading? If messing with pdflush (well, /proc/whatever) is a
bad idea too, where should I look for culprits so I can tweak the system
a bit and improve disk performance? I'm not 100% sure that the problem
is related *only* with the new kernel, but my problem is that I cannot
carry long tests (e.g. running a 2.4 for some days with my normal usage
pattern to see if the problem happens there: it doesn't happen in a
fresh boot 2.4 and it happens in a fresh boot 2.6)
Thanks a lot in advance, and feel free to ask whatever you need to
lend a hand O:)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
next reply other threads:[~2007-05-17 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 10:03 DervishD [this message]
2007-05-17 10:19 ` usb-storage nice value Alan Cox
2007-05-17 10:34 ` DervishD
2007-05-17 19:53 ` Stefan Richter
2007-05-18 6:15 ` DervishD
2007-05-18 6:33 ` Jan Engelhardt
2007-05-18 8:21 ` DervishD
2007-05-18 8:49 ` Jan Engelhardt
2007-05-18 11:13 ` DervishD
2007-05-18 9:46 ` Heikki Orsila
2007-05-18 11:12 ` DervishD
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=20070517100308.GA14667@DervishD \
--to=lkml@dervishd.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