> -----Original Message----- > From: Andi Kleen [mailto:[EMAIL PROTECTED]
> > You just need to make sure that you don't leak data from > other peoples > > sockets. > > There are three basic ways I can see to do this: > > - You have really advanced hardware which can potentially > manage tens of thousands of hardware queues with full > classification down to the ports. Then everything is great. > But who has such hardware? > Perhaps Leonid will do it, but I expect the majority of Linux > users to not have access to it in the forseeable time. Also > even with the advanced hardware that can handle e.g. 50k > sockets what happens when you need 100k for some extreme situation? > > -Andi You may be surprised here :-) iWAPP (RDMA over Ethernet) received a lot of funding and industry support over last several years, and rNIC development is already pre-announced by multiple vendors not just us. I expect RDMA deployment to be a long and bumpy multi-year road, since protocols and applications will need to change to take full advantage of it. And this is a discussion for a totally separate thread anyways :-) But in the meantime, these new ethernet adapters will have huge number of hw queue pairs (AKA channels), and at least some of the NICs will have these channels at no incremental cost to the hardware. You may be able to use the channels for full socket traffic classification if nothing else, and defer the rest of rNIC functionality until the iWARP infrastructure is mature. This is actually one of many reasons why VJ net channels and related ideas look very promising - we can "extend" it to the driver/hw level with the current NICs that have at least one channel per cpu, with a good chance that the next wave of hardware will support many more channels and will take advantage of the stack/NAPI improvements. Leonid - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
