Dedicated core(s) for network stack?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

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.

Thanks

Alex
--
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


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux