10 Terabit Ethernet By 2010
Eric Frost writes "From Directions Magazine: 'Because it is now impossible to sell networking unless it is called Ethernet (regardless of the actual protocols used), it is likely that 1 Terabit Ethernet and even 10 Terabit Ethernet (using 100 wavelengths used by 100 gigabit per second transmitter / receiver pairs) may soon be announced. Only a protocol name change is needed. And the name change is merely the acknowledgment that Ethernet protocols can tunnel through other protocols (and vice versa).'"
From the article: "iSCSI (Internet SCSI) over Ethernet is replacing: *SCSI (Small Computer Systems Interface..."
iSCSI is far superior to stadard SCSI for obvious reasons, and its widespread adoption will really spark a massive gain in the SAN (Storage Area Network) market. The technology is there, now we just need more major vendors of SCSI devices (especially storage and image filing systems) to make more SCSI devices that support iSCSI natively and applications that take advantage of it. Combined with practical solutions from vendors of network storage software like Veritas we could see some major spending in IT. And more money being spent on IT is always a good thing.
I don't keep up much with the progress of the Ethernet technologies at hand, so is it realistic to suppose that the practical implementation/creation of 100 Gigabit Ethernet, 1 Terabit Ethernet, and 10 Terabit Ethernet will be seperated by merely two years each?
"Because it is now impossible to sell networking unless it is called Ethernet". Incorrect. You can easily sell network gear that is tagged with the "WiFi" designation.
Is there going to be storage that can read/write that fast by 2010 too?
paintball
...is there going to be a bus on desktop machines that can read or write that fast?
Probably not. But I could definitely see it being useful for top-end server systems with hugely parallel storage and memory access.
Interestingly enough, if you did it wouldn't be a very big success because the internal PCI or PCI-X bus in the system would bottleneck the interconnects. The NICs would need on-board processors to scale with their enormous bandwidth potential so that they could solve problems like matching checksums and other package management tasks and not have to pound on the system bus so hard.
It wasn't long ago that we really started exploiting video chipsets for rendering graphics, either...
I am sure packetengines (http://www.scyld.com/network/yellowfin.html) is all over this.
These guys had gigabit routers four years ago when I was helping to set up the AFN (ashlandfiber.com)
Cool to see.. mo'faster is mo'betta
anime+manga together at last.. in real time.
100 ms latency would affect a 10Mbps network and a 10 Tbps network almost equally if a clustered application is using very small packets to communicate. Only if the application is using very large packets, the bandwidth will overcome the latency. At small packet sizes the latency will largely overshadow the bandwidth. And considering that a lot of scientific applications use small payloads, latency is very important. If ethernet wants acceptance in the High-Performance-Computing-Clusters world, something has to be done about the latency.
And that assumes that transfer occurs at chip speed, which it doesn't. Assuming a modest clock multiplier of 8 between system bus and chip, that's a 15x overcapacity, even if the entire computer were used to transmit.
-Looking for a job as a materials chemist or multivariat