Thread (87 messages) 87 messages, 12 authors, 2007-02-22

Re: [patch 07/21] Xen-paravirt: remove ctor for pgd cache

From: Jeremy Fitzhardinge <hidden>
Date: 2007-02-16 17:19:37
Also in: lkml, xen-devel

Nick Piggin wrote:
Pekka Enberg wrote:
quoted
On 2/16/07, Jeremy Fitzhardinge [off-list ref] wrote:
quoted
Remove the ctor for the pgd cache.  There's no point in having the
cache machinery do this via an indirect call when all pgd are freed in
the one place anyway.

The reason we have slab constructors and destructors is to _avoid_
reinitializing every time we allocate an object. AFAICT your changing
the code now to do _more_ work than before, so is there some other
reason why you want to do this than avoiding an indirect call?
Sometimes  it is better for the caches to initialise an object
immediately, but in this case I think it is better to use the
slab ctor because it is very unlikely to use many cachelines
immediately anyway.

It would be nice to put the "why" in the changelogs, rather than
"what". Not everyone wants to go through the whole patchset to
decipher why Xen possibly needs something.
Hm, I think I was mislead by looking at kmem_cache_alloc in slob.c
rather than the one that's actually used in slab.c.  There's no
particular Xen reason for this patch, so I can drop it.

    J
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help