archive mirror
 help / color / mirror / Atom feed
From: Matthew Dharm <>
To: Oliver Neukum <>
Cc: USB Developers <>,
	Kernel Developer List <>
Subject: Re: [linux-usb-devel] System stalls using usb-storage
Date: Sat, 26 Jul 2003 23:35:45 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>; from on Sun, Jul 27, 2003 at 08:24:44AM +0200

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

On Sun, Jul 27, 2003 at 08:24:44AM +0200, Oliver Neukum wrote:
> Am Donnerstag, 24. Juli 2003 05:00 schrieb Matthew Dharm:
> > Many people, including myself, have observed system stalls when using
> > usb-storage.  It happens when copying large amounts of data to a USB device
> > -- everything (except the USB access) just stops for a little while.  My
> > best guess is that the block cache is filling up (easy since USB is so
> > slow).
> Can you do a vmstat run? That should provide conclusive data.
> If so, write throteling is failing.

I'll set up some tests and get back to you...

> > The question is, what is the best way to handle this.  I'm guessing that
> > increasing the priority of the usb-storage control thread will help, but
> > that's just a guess.  I'm not even sure how to go about doing that, tho...
> A kernel thread in the block io path has to have a higher priority than
> any user task. Otherwise a priority inversion is possible.

Reasonable.  So, other than renice at the command line, how does one go
about setting this?


Matthew Dharm                              Home: 
Maintainer, Linux USB Mass Storage Driver

Somebody call an exorcist!
					-- Dust Puppy
User Friendly, 5/16/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2003-07-27  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  3:00 System stalls using usb-storage Matthew Dharm
2003-07-27  6:24 ` [linux-usb-devel] " Oliver Neukum
2003-07-27  6:35   ` Matthew Dharm [this message]
2003-07-27  9:09     ` Peter Osterlund

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).