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, 04 Mar 2013 17:28:27 +0200 From: Eliezer Tamir <eliezer.tamir@...ux.intel.com> To: Eric Dumazet <eric.dumazet@...il.com> CC: Eliezer Tamir <eliezer.tamir@...ux.jf.intel.com>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Dave Miller <davem@...emloft.net>, Jesse Brandeburg <jesse.brandeburg@...el.com>, e1000-devel@...ts.sourceforge.net, Willem de Bruijn <willemb@...gle.com>, Andi Kleen <andi@...stfloor.org>, HPA <hpa@...or.com>, Eliezer Tamir <eliezer@...ir.org.il> Subject: Re: [RFC PATCH 1/5] net: implement support for low latency socket polling On 04/03/2013 16:52, Eric Dumazet wrote: > On Mon, 2013-03-04 at 10:43 +0200, Eliezer Tamir wrote: > >> One could for example increment the generation id every time the RTNL is >> taken. or is this too much? > > RTNL is taken for a lot of operations, it would be better to have a > finer grained increment. If is taken rarely enough it will still be worth it. Otherwise it may be hard to know what operations need to invalidate the napi reference. It can very well be HW dependent, and then you end up adding a function for drivers to call to do the invalidation. Or we can decide that we only care about catastrophic events and only worry about a napi completely going away and not worry about configuration changes.(Polling the wrong queue will not kill you, it's just a waste of perfectly good CPU cycles.) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists