" turtle: Right now Intel needs to focus on the fact not only is it something they will support, but also set a baseline of what the expected feature set should be. "
agreed, what is it with Intel anyway, we have known for years their Thunderbolt port IP came with 4 possible ports internally and that its in effect talking to the next device in the FB chain over a virtual PCIe bus and yet we still only get a poultry One Thunderbolt port on PC's years later, you need 2 at the very least so you can daisy chain the devices together.
its like they don't want you to actually buy it and so make Thunderbolt a real world standard.
and why have they still not written the generic Ethernet over Thunderbolt drivers given for instance that their other interesting card is the Knight's Corner Co-Processor that uses vanilla TCP/IP over PCIe internally to/from all its cores.
so put these NC's in your Thunderbolt equipped desktop and talk to the other daisy chained Thunderbolt devices like this with Ethernet over Thunderbolt drivers , its so obvious , why dont Intel write the damn thing and mandate 2 daisy chained Thunderbolt ports per Intel device peripheral from now on,you cant make a standard by price gouging to start with (that comes later like apple) you know Intel should be doing a "special buy one Thunderbolt part get one free type of offer to the OEM's"
"KC has an OS running on it, in this case it is a single Linux image per chip. Larrabee and Knights Ferry, the architecture that preceded KC, used a BSD based OS. The OS runs can be SSH’d to, and can run code just like a standalone CPU, but most users won’t use it in that way. That OS is presented with an interface that looks like a standard TCP/IP software stack, but there is no reason why it could not be hardware based in the future. If you have multiple KC cards in a server, they tunnel vanilla TCP/IP over PCIe.
In case it isn’t obvious, the standard way to do clustering on a rack of PC servers is with MPI, and that uses TCP/IP to talk between nodes."
ohh i see down voted as its too complicated to comprehend perhaps , these NUC are billed as special purpose and price, so Thunderbolt port x2 + generic Ethernet over Thunderbolt drivers = daisy chained generic (up to)10 gigabit
TCP/IP Ethernet speed between all Thunderbolt connected (NUC and DT)PC's
if TCP/IP Ethernet over USB with the existing generic Linux USB-eth interface was good enough for the old mobile iPAQ back in the day http://en.wikipedia.org/w...SB_as_an_Ethernet_network
then why would you not want and demand a free windows/Linux driver that gives you up to 10 gigabit TCP/IP Ethernet speed between all Thunderbolt connected PC's today given the current price gouging of all Thunderbolt kit today