On Wed, 16 Sep 2015, Jesper Dangaard Brouer wrote: > > Hint, this leads up to discussing if current bulk *ALLOC* API need to > be changed... > > Alex and I have been working hard on practical use-case for SLAB > bulking (mostly slUb), in the network stack. Here is a summary of > what we have learned so far. SLAB refers to the SLAB allocator which is one slab allocator and SLUB is another slab allocator. Please keep that consistent otherwise things get confusing > Bulk free'ing SKBs during TX completion is a big and easy win. > > Specifically for slUb, normal path for freeing these objects (which > are not on c->freelist) require a locked double_cmpxchg per object. > The bulk free (via detached freelist patch) allow to free all objects > belonging to the same slab-page, to be free'ed with a single locked > double_cmpxchg. Thus, the bulk free speedup is quite an improvement. Yep. > Alex and I had the idea of bulk alloc returns an "allocator specific > cache" data-structure (and we add some helpers to access this). Maybe add some Macros to handle this? > In the slUb case, the freelist is a single linked pointer list. In > the network stack the skb objects have a skb->next pointer, which is > located at the same position as freelist pointer. Thus, simply > returning the freelist directly, could be interpreted as a skb-list. > The helper API would then do the prefetching, when pulling out > objects. The problem with the SLUB case is that the objects must be on the same slab page. > For the slUb case, we would simply cmpxchg either c->freelist or > page->freelist with a NULL ptr, and then own all objects on the > freelist. This also reduce the time we keep IRQs disabled. You dont need to disable interrupts for the cmpxchges. There is additional state in the page struct though so the updates must be done carefully. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>