On Sun, 05 Sep 2010 15:08:52 +0200 (CEST) ales-76@xxxxxxxxx wrote: > Hello, > > Recently I've read some nice articles: > > Shalev L. et al., IsoStack - Highly Efficient Network Processing on Dedicated Cores > http://www.usenix.org/event/atc10/tech/full_papers/Shalev.pdf > Regnier G. et al., ETA: Experience with an Intel Xeon Processor as a Packet Processing Engine > http://www.hoti.org/archive/Hoti11_program/papers/hoti11_11_regnier_g.pdf > Regnier G. et al., TCP Onloading for Data Center Servers > ftp://download.intel.com/technology/comms/perfnet/download/tcp_ieee_article.pdf > > Very interesting reading, I guess that many kernel people are familiar with these papers. Anyway my question is: > > Any considerations (or even ongoing project) for implementing similar TCP/IP stack architecture under Linux? No explicit project but it is an interesting idea. > It looks to me like very brigth idea, especially when number of cores on-chip increases every year and the trend is clear. The benchmark seems to indicate that isolating a core (or more) solely for network processing is a big win in terms of performance. I am curious what is the opinion of kernel developers on this. There is a myth that "network processing" is a some sort of monolithic entity with a single use case. For a typical server/client, there interactions of scheduler local processes and caching. If the processing is on a dedicated core, it guarantees a cache miss when the data is processed by the application. -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
