tree 5d501aa83869f533c92addd23233eb274f7fb36a
parent be5707e19ee2ae0bb7f39e5be1501fcbc4259e83
author Barret Rhoden <brho@cs.berkeley.edu> 1567024843 -0400
committer Barret Rhoden <brho@cs.berkeley.edu> 1569939421 -0400

slab: add kmem_cache_zalloc()

You could argue that the caller could do this with a ctor, though it
depends on when we run the ctors.  Do we cache constructed objects in
magazines?  I'd guess 'yes', without a lot of thought, so then each
separate allocation wouldn't be zeroed.

The other reason to make a separate function for this is that it's
easier to just implement it.  We have the object size in the kc, but the
ctor function pointer actually *doesn't* have that info, so we'd need to
pass it through.  Minor pain, chance to mess it up, etc.

The other other reason is that Linux has this function.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>