Hi Johannes,
On Mon, 2009-02-16 at 14:56 +0100, Johannes Weiner wrote:
> On Tue, Feb 10, 2009 at 04:06:53PM +0200, Pekka J Enberg wrote:
> > On Tue, Feb 10, 2009 at 03:35:03PM +0200, Pekka Enberg wrote:
> > > > We unexported ksize() because it's a problematic interface and you
> > > > almost certa
On Tue, Feb 10, 2009 at 04:06:53PM +0200, Pekka J Enberg wrote:
> On Tue, Feb 10, 2009 at 03:35:03PM +0200, Pekka Enberg wrote:
> > > We unexported ksize() because it's a problematic interface and you
> > > almost certainly want to use the alternatives (e.g. krealloc). I think
> > > I need bit more
On Mon, 2009-02-16 at 14:56 +0100, Johannes Weiner wrote:
> One problem is that zeroing ksize()
> bytes can have an overhead of nearly twice the actual allocation size.
A possible good thing is when linux has a
mechanism to use known zeroed memory in
kzalloc or kcalloc, it's already good to go.
-
On Mon, 2009-02-16 at 14:56 +0100, Johannes Weiner wrote:
>> One problem is that zeroing ksize()
>> bytes can have an overhead of nearly twice the actual allocation size.
On Mon, Feb 16, 2009 at 6:32 PM, Joe Perches wrote:
> A possible good thing is when linux has a
> mechanism to use known zeroe
