public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Linux usb mailing list <linux-usb-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] *BAD* impact of usb on PCI performance
Date: Sun, 03 Jun 2001 09:00:24 -0700	[thread overview]
Message-ID: <013e01c0ec46$4d3727a0$6800000a@brownell.org> (raw)
In-Reply-To: <20010602132200.A186@bug.ucw.cz>

> From: "Georg Acher" <acher@in.tum.de>
> On Sat, Jun 02, 2001 at 01:22:00PM +0200, Pavel Machek wrote:
> > 
> > With Acher's uhci, even ifconfig up of usb-to-usb networking device
> > [plusb handled by generic usb-to-usb driver; see -ac series].
> > does 50% slowdown. When fsbr is being used, systems slows down by 350%
> 
> Hm, the 50% make me curious... have to look what's happening...

For PL-2301/2302 devices, "ifconfig up" is mostly just posting a bulk read.
True with both "usbnet" and its (now obsolete) predecessor drivers "plusb"
and (for different devices) "net1080".

Laplink-style cables can often support another mode (poll via USB "interrupts",
and then issue reads only when data is available) but not every device can work
that way (like, I seem to recall, an iPaq PDA).  And that'd increase the latency
per packet by a couple milliseconds, even when it's possible.


> > (running more than 4 times slower than normally. Ouch).
> 
> Blame Intel. Either low latency or low PCI usage, you can choose...

This problem is UHCI-specific, not USB-generic, yes?
Doesn't happen with OHCI?

- Dave




      reply	other threads:[~2001-06-03 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-02 11:22 *BAD* impact of usb on PCI performance Pavel Machek
2001-06-03 16:00 ` David Brownell [this message]

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='013e01c0ec46$4d3727a0$6800000a@brownell.org' \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.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