From: David Brownell <david-b@pacbell.net>
To: Oliver.Neukum@lrz.uni-muenchen.de
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, Greg KH <greg@kroah.com>
Subject: Re: [linux-usb-devel] Re: highmem and usb [was:"sr: unalignedtransfer" in 2.5.2-pre1]
Date: Wed, 02 Jan 2002 10:43:33 -0800 [thread overview]
Message-ID: <07db01c193bd$62191ec0$6800000a@brownell.org> (raw)
In-Reply-To: <Pine.SOL.4.33.0201021018550.4555-100000@sun2.lrz-muenchen.de>
> > > I'd rather eliminate as much overhead as possible -- I already get
> > > complaints from performance fanatics about the inability of usb-storage to
> > > get past 92% bus saturation (sustained), and the problem will only get
> > > worse on USB 2.0
> >
> > Well then you'll be glad to see a patch from me, soonish, that teaches
> > the usb-storage "transport" code to use bulk queueing. That'll get the
> > bandwidth utilization up as high as it can get. It won't address any of
> > these highmem issues though.
>
> And there's the overhead of sleeping and waking a kernel thread. Larger io
> requests might help, but I am not sure.
Yes, it's that sleep/wake between scatterlist segments that's creating
that 92% (at 12 Mbit/sec) or about 20% (at 480 Mbit/sec :) bottleneck ...
Convert those calls to use bulk queuing, and those delays vanish.
- Dave
next prev parent reply other threads:[~2002-01-02 18:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-23 17:44 "sr: unaligned transfer" in 2.5.2-pre1 Peter Osterlund
2001-12-23 19:22 ` Greg KH
2001-12-30 9:31 ` Peter Osterlund
2001-12-30 11:27 ` Jens Axboe
2001-12-31 5:27 ` Matthew Dharm
2001-12-31 11:51 ` Jens Axboe
2001-12-31 22:54 ` [linux-usb-devel] " Matthew Dharm
2001-12-31 23:59 ` Andre Hedrick
2002-01-01 17:39 ` Jens Axboe
2002-01-01 17:40 ` Jens Axboe
2002-01-01 19:53 ` David Brownell
2002-01-01 22:34 ` Jens Axboe
2002-01-01 23:28 ` Matthew Dharm
2002-01-02 5:40 ` [linux-usb-devel] Re: highmem and usb [was: "sr: unaligned transfer" in 2.5.2-pre1] David Brownell
2002-01-02 9:27 ` [linux-usb-devel] Re: highmem and usb [was:"sr: unalignedtransfer" " Oliver.Neukum
2002-01-02 18:43 ` David Brownell [this message]
2002-01-02 9:31 ` [linux-usb-devel] Re: highmem and usb [was: "sr: unaligned transfer" " Jens Axboe
2002-01-02 9:30 ` [linux-usb-devel] Re: "sr: unaligned transfer" in 2.5.2-pre1 Jens Axboe
2002-01-02 5:27 ` [linux-usb-devel] Re: highmem and usb [was "sr: unaligned transfer" in 2.5.2-pre1] David Brownell
2002-01-02 9:32 ` Jens Axboe
2002-01-02 18:37 ` David Brownell
2002-01-02 18:44 ` Jens Axboe
2002-01-02 18:55 ` David Brownell
2002-01-02 20:23 ` Jens Axboe
2002-01-02 22:32 ` [linux-usb-devel] Re: highmem and usb [was "sr: unalignedtransfer" " Oliver.Neukum
2001-12-24 4:05 ` "sr: unaligned transfer" in 2.5.2-pre1 Bob_Tracy
2001-12-24 7:24 ` Peter Osterlund
2001-12-24 14:13 ` WHICH MACHINE????? Astinus
2001-12-24 15:37 ` Erik Mouw
2001-12-25 15:41 ` Svein Ove Aas
2001-12-26 13:56 ` Erik Mouw
2001-12-24 16:19 ` J.A. Magallon
2001-12-24 22:48 ` "sr: unaligned transfer" in 2.5.2-pre1 Peter Osterlund
2001-12-27 7:13 ` Petr Titera
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='07db01c193bd$62191ec0$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=axboe@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox