Slashdot Log In
USB 3 in 2008, 10 Times as Fast
Posted by
CmdrTaco
on Wed Sep 19, 2007 07:18 AM
from the i'll-believe-it-when-it's-on-my-laptop dept.
from the i'll-believe-it-when-it's-on-my-laptop dept.
psychicsword writes "Intel and others plan to release a new version of the ubiquitous Universal Serial Bus technology in the first half of 2008, a revamp the chipmaker said will make data transfer rates more than 10 times as fast by adding fiber-optic links alongside the traditional copper wires." "The current USB 2.0 version has a top data-transfer rate of 480 megabits per second, so a tenfold increase would be 4.8 gigabits per second." This should make USB hard drives easier and faster to use."
Related Stories
[+]
Hands-on Look At USB 3.0, Spec Details Revealed 251 comments
notdagreatbrain writes "Maximum PC dug up some new information about USB 3.0, got their hands on the new connectors, and even took a look inside the new cables. They learned several new details about the next-gen version of the ubiquitous interface. USB Superspeed will be backward compatible with USB 2.0. The maximum speed of the new spec is 4.8Gbps, which is ten times faster than hi-speed. Five new wires are bundled in the cable, four of them used for data transfer (bi-directional transfer is now supported). More power will also be funneled through the line, so you can charge more devices, faster. The wireless USB is also getting upgraded to version 1.1, and will include ultra-wide band frequency support and Near Field Communication for near-instant swipe-based syncing."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Great. (Score:3, Interesting)
Cue the Media Copying Discussions.
(Someone fast on their math: How long would that take to copy a new 0.90 Terabyte drive?)
Re: (Score:3, Informative)
Re:Great. (Score:5, Informative)
Parent
Re:Great. (Score:5, Informative)
On top of that, most hard drive controllers are limited by the technology they use. For instance, a SATA hard drive, even plugged into a USB 2 or 3 port, is limited to 150 MB/s -- but, that's burst speed, not sustained transfer rate.
Indeed. And realistically, it's going to be a pretty short burst: most hard drives today only have something like 8–16MB of cache that might be filled by a smart lookahead algorithm, so your best case with current hard drive technology is that you'll get perhaps 1/10 of a second of high-speed data transfer before hitting the physical barriers.
I'm not sure this is directly applicable to this discussion, though, because AFAIK all current USB drives use different storage technology anyway. It's going to be the limits of that technology that tell us whether USB3's theoretical speeds will actually be useful with storage hardware available in the same time frame.
Parent
0.9 TB / 4.8 Gb/s = 1500 seconds (Score:5, Informative)
Parent
Re:Great. (Score:5, Insightful)
Parent
Re:Great. (Score:5, Insightful)
No Flash is slow to write , very fast to read. Hence Windows use of it for "ReadyBoost" caching. There is extremely low latency just not enough bandwidth to sustain high levels of I/O.
On the other hand , by introducing fiber into the link doesn't that take away the greatest part of usb ? being able to just fold up the cable and stuff it in your pocket along with a small hard drive ? I know I use it for restoring machines after catastrophic failures (yeah windows) and some times I don't go right back to my desk with the cable and drive and have to toss it in my pocket. I can't do that with fiber, it would fracture.
Parent
Re: (Score:3, Informative)
Re:Great. (Score:4, Funny)
The RIAA and MPAA just joined Steve Balmer in needing new office furniture.
Parent
How exciting (Score:3, Funny)
obligatory simpsons quote (Score:3, Funny)
I'm more concerned with latency. (Score:5, Informative)
480Mbit per second = 60MByte per second. That can handle the average case for a modern hard drive.
4.8GBit/second - 600MByte/s? To utilize that with a drive, you'd need a RAID external enclosure!
Re:I'm more concerned with latency. (Score:5, Interesting)
Parent
Re:I'm more concerned with latency. (Score:5, Informative)
Parent
Re:I'm more concerned with latency. (Score:5, Interesting)
Parent
Re:I'm more concerned with latency. (Score:5, Interesting)
Bonus points if you hook a 108mb/s wireless lan adapter via USB and throw some large data files over it, watch your data speeds closely, and monitor system performance even closer.
Firewire (1394, ilink, DV port, whatever) really was the shit, not only fast, low overheads AND its a peer-2-peer setup, in a pinch you could daisy chain PCs with it for an impromptu 400mb/s lan.
Why didn't they just hang USB out to dry and get power into the eSATA spec and use that? At least then no extra chips would be needed on a mobo, external HDD would hookup with no loss in performance and we might finally see thumb drives that work natively with ANY os as... drives.
Parent
Size? (Score:3, Insightful)
Bottleneck? (Score:5, Insightful)
Re:Bottleneck? (Score:5, Insightful)
Which doesn't give me high hopes for USB3. High-speed links are all good and well, but if they keep including cheap-ass controllers, what's the point?
Parent
Re:Bottleneck? (Score:5, Insightful)
Firewire has both synchronous and asynchronous modes. In async mode, a bunch of packets can be transmitted before any acknowledgment back is required. That's bad if the cables is flakey, since it will result in a lot of retransmits, but bad firewire cables are the exception, not the rule. So async is almost always way more efficient than synch. I'm pretty certain that you are using the async mode for talking to your disk.
Parent
Yeah, but.. (Score:3, Insightful)
Re:Yeah, but.. (Score:5, Insightful)
Parent
In such an event... (Score:3, Insightful)
Re:Yeah, but.. (Score:5, Interesting)
When I was working on my Master's thesis, I had to splice optical fiber a few times. Believe me, it's not easy.
Glass fiber is very flexible. You can bend it in any way you want, it won't break. You can cut it, but that takes considerable force. If you break the fiber, you'll break the copper wires as well.
Personally, I think the weakest point in such a cable will be the connectors. Getting the light from one fiber to another requires careful alignment. Any deviation might causes loss of signal. Getting dirt into the connector is probably fatal.
Parent
oh goodie (Score:3, Funny)
The irony... (Score:3, Funny)
In today's news, vendors worldwide urged one another to move quickly and get IPv6 deployed by the year 2025. When asked about the one or two year lag between the release of specs and the availability of the technology, vendors quickly pointed out the timeframe it took to implement Packet Over Bongo [eagle.auc.ca] and IPv6 for Refrigerators [glocom.org]. "It's been a long time in the making (IPv6) but we've finally succeeded in getting console connectivity to the fridge. We can now via a command prompt: finger lettuce" stated the happy refrigerator engineer. We never even knew of the existence of IPv4 for refrigerators. Engineers estimate another 20-80 year wait for IPv6.
Plug Shape (Score:5, Insightful)
While I appreciate USB's capability for backwards computability, I would much rather have a plug shaped in such a way that I didn't have to flip it over every time I try to plug it in. I don't know about you guys but this is one of the most annoying aspects of using my computer, and I run Windows!
This would also be a great time to make a universal "other side" of the cable, rather than having a different plug for every single USB device. I have a mini plug for my camera, a big square one for my printer, a 2.5 mm jack to charge my MP3 player, etc. All these cables make a mess. If all my devices could share one cable, I'd be much happier.
Re:Plug Shape (SCSI was worse) (Score:3, Insightful)
Re: (Score:3, Insightful)
Seriously, the connector should have double the number of pins as it needs, and they should be symmetrical. That would also increase reliability, because if the cable didn't work one way because of a bad pin, just flip it over until you can buy a new cable.
Re: (Score:3, Insightful)
All the others with 2.5mm and other proprietary ends that work on nothing else are solely the fault of the OEMs. Nobody asked them to do it, it never made sense to do it, and it's just a huge pain in the ass for everyone.
It makes a whole lot of sense to an OEM who wants to be the only one who can sell their customers a cable despite an open standard. It's the same reason for every standard out there which suppliers have taken it upon themselves to add their own "enhancements" to.
Re:Plug Shape (Score:4, Insightful)
I don't think the idea is to have the cable flippable, but instead to have some indication in the shape of which way around it goes. Firewire connects have a rounded end and a squared off one, for example.
Parent
Re:Plug Shape (Score:4, Insightful)
Parent
More half assed implementations. (Score:3, Insightful)
Faster, possibly (Score:3)
But easier? How would it make using external HDDs easier?
Screw bandwidth... (Score:5, Insightful)
Re: (Score:3, Informative)
So we should be able to boot from a USB flash (Score:3, Interesting)
Honest Question (Score:5, Interesting)
I've got a question that has been nagging at me for quite a while and was hoping someone here could phrase an answer in terms a mere mortal could understand.
We've got, off the top of my head, SCSI, USB, Ethernet, FireWire, and SATA to name a few. I do understand there are different protocols (all the way up from the physical to the application layers). Different applications of these technologies permit some optimizations that might not be applicable in other situations. But, at some point, the underlying technology is fast enough
Still, I can't help but think there should be some common denominator that ALL these communications standards can agree on, and through economies of scale, become universal standard(s). It just seems like people keep re-inventing the wheel with an eye toward THEIR favorite.
I thought we were getting close when they released gigabit Ethernet over UTP (unshielded twisted pair).
So, for the sake of argument, why not have all of our serial devices just support gigabit Ethernet? Sure, you'd need a hub or switch in your PC to talk to all of the devices, but you already need something similar for the other protocols (USB hub, SCSI controller, etc.). It's a well-known technology with many implementations and is widely available. I'd willingly pay a few more bucks for each device if I could ditch all of these incompatible formats and just standardize on one SET of ports and cables for hooking things to (and within) my PC. And in those cases where a different connector is desired (e.g. for small form-factor devices like a digital camera), let me just get an adapter cable/plug that I can plug into my Ethernet port.
Is there any good, technical reason that is keeping us from having truly UNIVERSAL serial communications?
Re:Honest Question (Score:4, Interesting)
USB connectors are designed to be inserted and removed over and over. They're held in by pressure against the connector, so they can be removed without having to push a tab or twist the connector to remove it.
UTP cables are designed to be plugged in, and then generally left alone. The UTP cable in my computer bag is in terrible shape.. the RJ45 connector is coming loose, the plastic retaining tab is broken off (so the cable often pops out of the jack on its own), etc.
I have USB devices which I've removed and inserted hundreds of times, and the connectors still work reliably.
Parent
Re:Honest Question (Score:5, Informative)
Obviously each manufacturer wants you to use their standard and buy their hardware.
Different implementations came through at different times, and have different amounts of software/hardware overheads, and try to do different things.
RS232 has almost no necessary software overhead -- you do any and all the work with code you write. USB has *quite* a bit of software overhead to deal with device identification, and Ethernet has *enormous* amounts of overhead. In most small systems you have to buy an Ethernet software stack separately from the OS you're using.
USB tries to provide power. People are trying to glue power into Ethernet although it hasn't yet taken off.
People keep going off in odd wireless directions.
The fundamental problem, I think, is that there are several different connectivity needs and manufacturers are trying to get you to buy their solution to what they think are the most important needs. What you're asking for is something good for the industry in the long term, and that's not really in the direct interest of any particular company, so nobody's building anything for it.
The military embedded market seems to be moving towards gigabit or 10-gig fiber ethernet for all their interboard communications, but fiber has its own problems, and I'm not sure it's the right thing for a USB key you're carrying in your pocket all the time.
I believe that the SCSI module in linux handles firewire and USB, so from that standpoint it looks like it's a start towards universal communications, except for Ethernet. (Even though old SCSI is nothing like serial: it's the the ultimate expression of parallel communications, with some similarities to the old HP/GPIB parallel communication standard that's still used in for test communication but used to be a hard drive standard.) I have no idea what Windows does.
Parent
Re:Honest Question (Score:5, Interesting)
Is there any good, technical reason that is keeping us from having truly UNIVERSAL serial communications?
Yes.
Let me explain:
So, the reason why we don't have a universal serial standard is because the different interfaces were designed with different goals in mind.
Parent
Re:Honest Question (Score:4, Insightful)
Parent
Hope they do a better job on compatibility (Score:3, Interesting)
I've been seriously disappointed with the number of times I've interconnected USB 1.1 and USB 2.0 devices and had them almost work, only to encounter various strangeness and glitches. I don't know who's to blame... whether it's a fault in the standard or in vendors' faulty implementations... and life's too short to care, because know who's to blame wouldn't do much to help solve the problem.
On the whole, I blame the standard, because these days standards are so incredibly huge, bloated, and complex that it is extremely unlikely that anyone actually implements it fully correctly.
With today's sloppy practices of testing to the market ("Let's try it with the most popular devices, or the ones which are most important to our business") instead of testing to the standard, the result is all sorts of opportunities to build devices that comply with the standard but do things just a little differently than the most popular devices... and have them not work even though they "should."
A typical example was an IOmega external CD burner I bought once for a USB 1.1 Mac. (I chose it because it was $30 cheaper than a FireWire model, I wanted both PC and Mac present and future compatibility), and I didn't really care about speed. The drive actually burned perfect CDs, but it always claimed erroneously that an error had occurred. But how could a sane person rely on that? I returned it, bought a different USB 2.0 external CD burner from a different vendor... and encountered exactly the same problem.
I've also seen various glitches and strangenesses trying to use USB 1.1 thumb drives in USB 2.0 CPUs and vice versa.
Don't let the marketing guy name it this time. (Score:3, Interesting)
we're probably going to wind up with yet another ambiguous name like "Extreme Speed" or "Max Speed".
Just call it USB 3.0 and be done with it.
Re:Cable? (Score:5, Informative)
"It will be backward compatible, so current USB 2.0 devices will be able to plug into USB 3.0 ports."
Parent
Re:Cable? (Score:5, Informative)
This is wrong, if you plug a USB 1.1 device into a USB 2.0 "bus" then it does NOT slow everything down. Specifically there are 2 cases:
1. You plug a USB 1.1 device directly into your computer (i.e. directly into the "host controller"). In this case, the USB 2.0 host controller (technically a EHCI chip) does NOT talk to your device. Instead, the EHCI chip has one or more USB 1.1 host controller chips (technically either a OHCI or UHCI chip, and called a "companion" chip when inside a EHCI chip) and your USB 1.1 device is connected electrically to that controller. You device is not on the USB 2.0 (EHCI) bus.
2. You plug a USB 1.1 device into a USB 2.0 hub. In this case, the USB 2.0 hub creates a complete USB 1.1 environment specifically for your device. On the host-facing side of the USB 2.0 hub, all communication continues to take place at USB 2.0 (i.e. 480Mbps) speeds. When the host wants to talk to your USB 1.1 device, it uses what is called "split transactions" to talk to it. Basically (I'm simplifying), this involves sending a "start" packet to the USB 2.0 hub. Then, the USB 2.0 (EHCI) controller goes on to do other things, while the USB 2.0 hub initiates the transfer to your device at USB 1.1 speeds. And data transferred from the USB 1.1 device is stored temporarily in the USB 2.0 hub. Eventually the USB 2.0 (EHCI) host sends a "finish" packet to the USB 2.0 hub. If the USB 1.1 transation finished, the USB 2.0 hub responds successfully (either with the incoming data or a "ack" that the outgoing data was sent) which completes the transation.
(There is also a combination case of those, where the EHCI chip does not contain a "companion" USB 1.1 chip, but instead contains an internal USB 2.0 partial hub - the "transaction translator" part - that handles talking to USB 1.1 devices. For bus usage purposes, this is effectively the same as using an external USB 2.0 hub, since the USB 1.1 devices do not appear on the USB 2.0 bus.)
Parent
Re: (Score:3, Interesting)
Re:Eat into firewire not likley (Score:4, Interesting)
Parent
Re:Eat into SATA? (Score:4, Interesting)
Parent
Re:Anyone else here see a problem?? (Score:5, Funny)
Parent