Researchers Transmit Optical Data at 16.4 Tbps 2550km
Stony Stevenson writes "The goal of 100 Gbps Ethernet transmission is closer to reality with the announcement Wednesday that Alcatel-Lucent researchers have recorded an optical transmission record along with three photonic integrated circuits. Carried out by researchers in Bell Labs in Villarceaux, France, the successful transmission of 16.4 Tbps of optical data over 2,550 km was assisted by Alcatel's Thales' III-V Lab and Kylia, an optical solution company. The researchers utilized 164 wavelength-division multiplexed channels modulated at 100-Gbps in the effort."
There is another problem, and is actually the bottleneck of transmitting packets at high rates.
It doesn't really matters (yet, and considering Ethernet technology) if the BW of the fiber is a zillion Petabits/sec.
The problem is now at 1Gbps and 10Gbps in Ethernet technology, and is because the processor overloads with the amount of hardware interrupts. The processors that are general purpose have to waste too many clock cycles processing that much interrupts, the processors nowadays are superscalar [ http://en.wikipedia.org/wiki/Superscalar ]and every time the processor have to change the context (to attend an interrupt) has to do lots of things like unloading the registers, saving the context, loading the registers of the new process, and has to drop something out of the pipeline [ http://en.wikipedia.org/wiki/Pipeline_(computing) ] loosing performance.
Ethernet tech has a huge latency [ http://en.wikipedia.org/wiki/Latency_(engineering) ] and a stack that makes processing not so easy (if you look at te code of a linux network device driver it handles pretty much everything including writing the mac address that is only copied when the driver initialize).
That is why there are some relative new things (NAPI in Linux) that try to make lessen the overload, there are new network devices that handle layer 2 and 3 (or at least parts of those, for example, is used to be handled the checksum algorithm) to avoid doing it in the processor. There are some white papers (one from intel, another from NetXen, I'm sorry I don't have the links now) that explain the problem and some approach to a possible solution.
Yes, I know, there is something I have not said, and is that the main switches or routers have to deal with that and have hardware specially designed to do heavy network packet processing, and that is the point, the network cards will have to do that (and are already starting to), neither is an easy job for hardware designers, nor for the market, is easier and cheaper to have a machine that you can change the behaviour only changing the firmware or changing settings from a program (routers have an operating system, and lots of those are a general purpose microprocessor with a linux kernel and a web server to configure it, for example home routers).
There is much to say yet in this field.