mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@in.ibm.com>
To: 7eggert@gmx.de
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Date: Tue, 21 Mar 2006 08:55:20 +0530	[thread overview]
Message-ID: <20060321032520.GB8954@in.ibm.com> (raw)
In-Reply-To: <E1FLPjT-0000o9-Sy@be1.lrz>

> > Ok, please keep the interface - build kmem_cache_zalloc() on top of
> > what I suggest.
> 
> The benefit of using *zalloc is the ability to skip the memset by using
> pre-zeroed memory or to use more efficient ways of zeroing a page.
> Having to check the value of a parameter wouldn't help.

Hmm... the current patch directly does a memset(). Are you talking about
possible optimizations to kmem_cache_zalloc()?

Balbir

  reply	other threads:[~2006-03-21  3:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5Ssjj-314-69@gated-at.bofh.it>
     [not found] ` <5Sv7o-7l5-23@gated-at.bofh.it>
     [not found]   ` <5Svh9-7xW-61@gated-at.bofh.it>
     [not found]     ` <5SvK8-88q-41@gated-at.bofh.it>
2006-03-20 19:07       ` Bodo Eggert
2006-03-21  3:25         ` Balbir Singh [this message]
2006-03-21 10:51           ` Bodo Eggert
2006-03-21 11:32             ` Pekka J Enberg
2006-03-20 13:07 Pekka J Enberg
2006-03-20 13:51 ` Eric Dumazet
2006-03-20 14:21   ` Pekka J Enberg
2006-03-20 16:05 ` Balbir Singh
2006-03-20 16:14   ` Pekka Enberg
2006-03-20 16:45     ` Balbir Singh
2006-03-21  7:13       ` Pekka J Enberg
2006-03-21 10:36 ` Andrew Morton
2006-03-21 11:03   ` Pekka J Enberg
2006-03-21 18:35     ` Manfred Spraul
2006-03-21 18:37       ` Pekka Enberg
2006-03-21 11:25 ` Andrew Morton
2006-03-21 11:50   ` Pekka J Enberg
2006-03-21 16:30   ` Pekka Enberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060321032520.GB8954@in.ibm.com \
    --to=balbir@in.ibm.com \
    --cc=7eggert@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome