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: Fri, 4 Sep 2015 13:55:24 -0500 (CDT) From: Christoph Lameter <cl@...ux.com> To: Alexander Duyck <alexander.duyck@...il.com> cc: Jesper Dangaard Brouer <brouer@...hat.com>, netdev@...r.kernel.org, akpm@...ux-foundation.org, linux-mm@...ck.org, aravinda@...ux.vnet.ibm.com, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, iamjoonsoo.kim@....com Subject: Re: [RFC PATCH 0/3] Network stack, first user of SLAB/kmem_cache bulk free API. On Fri, 4 Sep 2015, Alexander Duyck wrote: > were to create a per-cpu pool for skbs that could be freed and allocated in > NAPI context. So for example we already have napi_alloc_skb, why not just add > a napi_free_skb and then make the array of objects to be freed part of a pool > that could be used for either allocation or freeing? If the pool runs empty > you just allocate something like 8 or 16 new skb heads, and if you fill it you > just free half of the list? The slab allocators provide something like a per cpu pool for you to optimize object alloc and free. -- 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