Re: Dedicated core(s) for network stack?

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

 



On Mon, 06 Sep 2010 03:03:03 +0200 (CEST)
ales-76@xxxxxxxxx wrote:

> Hello,
> 
> Thank you, I'll take a look at that. No academical research - I'm jjust curious :-) The cache interaction is of course big concern, but the general architecture described in the papers sidestep this by leaving the actual data copy for application core(s) - for both TX and RX. Please read the papers first. And of course this was meant for SMPs, I guess that for NUMA machines the interaction with memory subsystem might hamper scalability of such approach. For uniprocessors and smaller machines the traditional stack would most likely still be a better choice. 
> 
> Alex

Both papers are not really applicable to current Linux.
One is from 2004 on 2.4 and the other is about AIX.
This predates all of the Linux work on using multiple queues
and packet steering.


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