| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 10 Oct 2011 18:32:28 +0200 From: Andi Kleen <andi@...stfloor.org> To: Alexander Duyck <alexander.h.duyck@...el.com> Cc: Andi Kleen <andi@...stfloor.org>, Jeff Kirsher <jeffrey.t.kirsher@...el.com>, davem@...emloft.net, netdev@...r.kernel.org, gospo@...hat.com, sassmann@...hat.com Subject: Re: [net-next 02/11] igb: Use node specific allocations for the q_vectors and rings > The RR configuration is somewhat arbitrary. However it is still better > than dumping everyting on a single node, and it works with the > configuration when the rings numbers line up with the CPU numbers since > normally the CPUs are RR on the nodes. From what I have seen it does > work quite well and it prevents almost all cross-node memory accesses > when running a routing workload. Ok so it's optimized for one specific workload. I'm sure you'll find some other workload where it doesn't work out. I suppose it's hard to get right in the general case, but best would be if ethtool had a nice and easy interface to set it at least. However one disadvantage of that patch over the existing state of the art (numactl modprobe ...) is that there's no way to override the placement now. So if you do the forced RR I think you need the ethtool part too, or at least some parameter to turn it off. -Andi -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists