Forgot your password?
typodupeerror

Comment Re:What's in a name... (Score 1) 231

Each device gets to use more bandwidth.

This isn't true. Linux doesn't allocate more bandwidth to devices than Windows. It follows the same bandwidth allocation rules (e.g. 10% of bandwidth is reserved for control transfers). If anything the USB stack and drivers are just faster and more efficient.

Do you have some benchmarks to back that up? The best I have seen with Linux is around 25MB/s (that was a couple of years back though), with XP x64 (which is more or less Windows 2003) I get 32MB/s with a good enclosure.

Here's a video the same demo with a USB 2.0 drive under EHCI. Linux shows 35MBps. Granted, I do need to run with some standard benchmark tools. ;)

Comment Re:What's in a name... (Score 3, Informative) 231

Hmm, a crappy host based implementation at 5Gbps or a storage targeted, low everhead one at 3Gbps (possibly going to 6Gbps if the next gen spec gets extended to eSATA), I know which one I will use =)

Actually, USB 3.0 was targeted for mass storage devices. They added the concept of Bulk Streams to support "out-of-order data transfers required for mass storage device command queuing." (USB 3.0 spec, section 4.4.6.4) Basically, the host can queue up to 65K SCSI commands, and the device can choose which command it wants to service first.

The host doesn't have to poll the device to see when commands are done because they added device notifications to USB 3.0. So the host fires off 65K of SCSI requests and the device asynchronously notifies the host as they get done. I'm no firewire expert, so I have no idea if it does something comparable. :)

Comment Re:latency badness (Score 2, Informative) 231

USB suffers from 1 ms time quantization and thus latency. I see nothing about fixing this.

Example badness:

When running MIDI over USB, timing is forced onto 1 ms slots. Normally when playing a chord, the keys don't all hit at exactly the same moment. You can't really tell, except that this makes the music sound natural. With the 1 ms problem, the keys happen at exactly the same moment (bad) or spread out into two separate events (worse).

Yes, USB 3.0 is still quantized. However, USB 2.0 devices can be sampled more often than 1ms. The 1ms frame was broken into 8 microframes in USB 2.0. I'm not a sound engineer, but it seems like you could have some buffering on the device side to send several sound samples with time stamps in one microframe. The software on the other side could re-space out the samples. Would you really notice a 125 us delay when playing music?

Linux Business

Submission + - Linux USB 3.0 demo (thesharps.us)

Sarah Sharp writes: "Intel's Open Source Technology Center is working on USB 3.0 support for Linux. USB 3.0 has wire speeds of 5Gbps and promises to be 10 times faster than USB 2.0. A recent a video demo shows speeds that are 3.5 times faster than USB 2.0. The USB 3.0 drivers will be submitted to the mainline kernel when the eXtensible host controller interface (xHCI) specification reaches a 1.0 release."

Slashdot Top Deals

This process can check if this value is zero, and if it is, it does something child-like. -- Forbes Burkowski, CS 454, University of Washington

Working...