On Thu, 22 Aug 2013 17:44:16 +0900
Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> wrote:
> With build-time size checking, we can overload the RCU head over the LRU
> of struct page to free pages of a slab in rcu context. This really help to
> implement to overload the struct slab over the struct page and this
> eventually reduce memory usage and cache footprint of the SLAB.
So I'm taking a look at this, trying to figure out what's actually in
struct page while this stuff is going on without my head exploding. A
couple of questions come to mind.
> static void kmem_rcu_free(struct rcu_head *head)
> {
> - struct slab_rcu *slab_rcu = (struct slab_rcu *)head;
> - struct kmem_cache *cachep = slab_rcu->page->slab_cache;
> + struct kmem_cache *cachep;
> + struct page *page;
>
> - kmem_freepages(cachep, slab_rcu->page);
> + page = container_of((struct list_head *)head, struct page, lru);
> + cachep = page->slab_cache;
> +
> + kmem_freepages(cachep, page);
> }
Is there a reason why you don't add the rcu_head structure as another field
in that union alongside lru rather than playing casting games here? This
stuff is hard enough to follow as it is without adding that into the mix.
The other question I had is: this field also overlays slab_page. I guess
that, by the time RCU comes into play, there will be no further use of
slab_page? It might be nice to document that somewhere if it's the case.
Thanks,
jon
--
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>