From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: OT: Why is usb data many times the cpu hog that firewire is?
Date: Thu, 24 Feb 2005 23:50:05 +0000 (UTC) [thread overview]
Message-ID: <cvlp7d$huv$1@terminus.zytor.com> (raw)
In-Reply-To: 200502211216.35194.gene.heskett@verizon.net
Followup to: <200502211216.35194.gene.heskett@verizon.net>
By author: Gene Heskett <gene.heskett@verizon.net>
In newsgroup: linux.dev.kernel
>
> Do I have something fubar in the usb? Or is this just the nature of
> the beast?
>
USB pretty much is fubar. It's a horrible protocol on pretty much
every level including the physical level.
-hpa
prev parent reply other threads:[~2005-02-25 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 17:16 OT: Why is usb data many times the cpu hog that firewire is? Gene Heskett
2005-02-21 17:58 ` Oliver Neukum
2005-02-21 18:25 ` Gene Heskett
2005-02-21 18:29 ` Wichert Akkerman
2005-02-21 22:08 ` Gene Heskett
2005-02-22 23:10 ` Matt Mackall
2005-02-23 13:13 ` Paulo Marques
2005-02-23 17:15 ` Geert Uytterhoeven
2005-02-21 18:40 ` Paulo Marques
2005-02-21 18:46 ` Oliver Neukum
2005-02-24 11:52 ` David Ford
2005-02-22 8:53 ` Barry K. Nathan
2005-02-22 13:12 ` Gene Heskett
2005-02-23 23:28 ` Bill Davidsen
2005-02-24 23:50 ` H. Peter Anvin [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='cvlp7d$huv$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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