| There is also the problem that 10gbe over copper requires interleaving, whereas optical doesn't. A lot of 10gbit uses are latency sensitive. 2.5 and 5 usage is not likely to be latency sensitive usage. 2.5 and 5 are based on the existing 10gbase-t technology, and can be deployed over existing Cat5e and Cat6, whereas 10gbase-t only works reliably over existing Cat6 sometimes less than 100ft. 802.3bz's genius is basically running 10gbase-t at half or quarter the clock speed, requiring lower spec cabling but also lower power/lower heat parts. I don't know why this wasn't done as part of the original 10gbase-t specification (802.3an, which is now 10 years old; in comparison, 802.3ab, which defines 1gbase-t, is 17). In addition, for embedded hardware, 2.5 and 5 are a better fit for common on-chip SerDes implementations when you need to wire stuff up that way. As for power usage, a modern 10gbase-T controller ran at 1/4th the clockspeed (and voltage also appropriately adjusted) would use less than 1/4th the power, but be more power efficient than an existing modern 1gbase-t, per gbit/sec. The real question is, when will all the cheap "we need an ethernet port but nothing fancy" controllers (which are all gigabit in anything recognizable as a computer, 100mbit becoming more and more rare in anything not recognizable as a computer) become baby 10gbit? That's all I really care about. |