Re: Large slab cache in 2.6.1

[Mike Fedyk]

Jamie Lokier wrote:
> It's not totally insane to free dcache entries from pages that won't
> be freed.  It encourages new entries to be allocated in those pages.
>
> Ideally you'd simply mark those dcache entries as prime candidates for
> recycling when new entries are needed, without actually freeing them
> until new entries are needed - or until their whole pages can be
> released.

This doesn't do much when you want to actually free slab pages though...

I had a similair thought, where you'd mark slab pages where you should 
aggressively try to free the containing slab objects in future scans, 
but didn't send it since someone else had probably already thought of it.

> Also, biasing new allocations to recycle those old dcache entries, but
> also biasing them to recently used pages, so that recently used
> entries tend to cluster in the same pages.

Hmm, so if slab is on the LRU, then in some cases the page can't be 
freed because of locked slab objects and new objects get allocated to 
the new mostly free slab page, and you didn't free very many pages.

Though this might better utilize the slab pages...

Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/