All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Harald Dunkel <harri@synopsys.COM>,
	USB Storage List <usb-storage@one-eyed-alien.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.0-test1: random errors for USB disk
Date: Thu, 17 Jul 2003 12:58:08 -0700	[thread overview]
Message-ID: <3F16FFD0.9070905@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0307171520390.1251-100000@ida.rowland.org>

Alan Stern wrote:

> The information in your system logs is very clear.  Your USB drive worked 
> just great until it received a big data transfer.
> 
> Under 2.4, the largest WRITE transfer was 130048 bytes and it worked fine.  
> Under 2.6, the largest attempted WRITE transfer was 524288 bytes and it
> crashed the drive.  The two commands were otherwise identical.

Just to clarify:  there's another difference, and that's that 2.4 does
doing that smaller write one page at a time (write, wait, write, wait,...)
while 2.6 does it all at once (write, write, write, write, ... wait).

That difference is how I've seen usb-storage top 30 MByte/sec on USB
with 2.6 kernels, when 2.4 may not reach 10 MB/sec on the same hardware.

- Dave


> Presumably differences in the block I/O systems account for the difference
> in buffer sizes.  But I don't know of any way to tell Linux that the drive
> is unable to accept data transfers larger than some fixed limit.
> 
> Can anyone else suggest a way to solve this?
> 
> Alan Stern
> 
> 



  reply	other threads:[~2003-07-17 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3F16D933.2080607@Synopsys.COM>
2003-07-17 19:34 ` [linux-usb-devel] 2.6.0-test1: random errors for USB disk Alan Stern
2003-07-17 19:58   ` David Brownell [this message]
2003-07-17 20:47     ` Harald Dunkel

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=3F16FFD0.9070905@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=harri@synopsys.COM \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@one-eyed-alien.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.