Slashdot Mirror
Intel Announces Open Fibre Channel Over Ethernet
sofar writes "Intel has just announced and released source code for their Open-FCoE project, which creates a transport allowing native Fibre Channel frames to travel over ordinary ethernet cables to any Linux system. This extremely interesting development will mean that data centers can lower costs and maintenance by reducing the amount of Fibre Channel equipment and cabling while still enjoying its benefits and performance. The new standard is backed by Cisco, Sun, IBM, EMC, Emulex, and a variety of others working in the storage field. The timing of this announcement comes as no surprise given the uptake of 10-Gb Ethernet in the data center."
You're kidding right?
1. TCP/IP is all about getting packets in the right order. That is it's purpose. It will give the application the data in the correct order. That's why TCP was created. UDP does not guarantee order, TCP does. The reason you see stuttering in video is because the bitrate of the video is higher than the bitrate you may be getting over the wire. Also, if this is all happening on a local network, how and why would a packet not arrive in the right order and in nearly the same amount of time each time? If you were running an iSCSI setup you would (should) be running it on its own private network.
2. Jumbo frames...
3. Again, you're kidding right? I can find offloading cards for around $100, I can't find any good fibre channel cards for that price.
I think slashdot moderators hate me, why am I modded a 1 and the comment I'm replying to a 2??
Anyway, I'm not sure I follow what you're saying. The TCP stack on the sending machine most certainly sends the packets in order. Whether or no IP delivers them in order is a different matter and that's for TCP to fix. The thing is, TCP fixes the ordering issue BEFORE it sends the data up to the application so as far as the application is concerned, everything IS IN ORDER. The application will block (or timeout) until TCP is satisfied and sends it some data.
All of this ignores the idea that you probably aren't doing iSCSI through multiple routers and bridges. Nobody in their right mind is attempting to do iSCSI over the Internet and expecting fibre channel like performance. You've got some serious issues if you have packets that are out of order on your local network.