archive mirror
 help / color / mirror / Atom feed
From: Matthew Dharm <>
To: USB Developers <>,
	Kernel Developer List <>
Subject: System stalls using usb-storage
Date: Wed, 23 Jul 2003 20:00:51 -0700	[thread overview]
Message-ID: <> (raw)

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

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

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...

This is seen on 2.4 and 2.5/6 kernels.

Anyone have any ideas?


Matthew Dharm                              Home: 
Maintainer, Linux USB Mass Storage Driver

M:  No, Windows doesn't have any nag screens.
C:  Then what are those blue and white screens I get every day?
					-- Mike and Cobb
User Friendly, 1/4/1999

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

             reply	other threads:[~2003-07-24  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  3:00 Matthew Dharm [this message]
2003-07-27  6:24 ` [linux-usb-devel] System stalls using usb-storage Oliver Neukum
2003-07-27  6:35   ` Matthew Dharm
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).