From: Stephen Pollei <stephen.pollei@gmail.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, pmarques@grupopie.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] kernel: use kcalloc instead kmalloc/memset
Date: Fri, 5 Aug 2005 11:39:55 -0700 [thread overview]
Message-ID: <feed8cdd0508051139799ff4d5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0508051114001.31384@graphe.net>
On 8/5/05, Christoph Lameter <christoph@lameter.com> wrote:
> Hmm. If we had kcmalloc then we may be able to add a zero bit to the slab
> allocator. If we would obtain zeroed pages for the slab then we may skip
> zeroing of individual entries. However, the cache warming effect of the
> current zeroing is then not occurring. Not sure if this would make sense
> but this is a possible optimization if we had kcmalloc.
Well there is kzalloc and kcalloc. I just thought a safe non-zeroing
version would be nice.
You could warm the cache with prefetch, but you'd need to profile the
diferent cases to see what is worth doing and what isn't.
--
http://dmoz.org/profiles/pollei.html
http://sourceforge.net/users/stephen_pollei/
http://www.orkut.com/Profile.aspx?uid=2455954990164098214
http://stephen_pollei.home.comcast.net/
next prev parent reply other threads:[~2005-08-05 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 5:29 [PATCH] kernel: use kcalloc instead kmalloc/memset Pekka Enberg
2005-08-05 5:38 ` Andrew Morton
2005-08-05 6:30 ` Pekka J Enberg
2005-08-05 6:36 ` Andrew Morton
2005-08-05 6:52 ` Pekka J Enberg
2005-08-06 15:09 ` Adrian Bunk
2005-08-08 10:11 ` Takashi Iwai
2005-08-08 21:05 ` Adrian Bunk
2005-08-09 10:09 ` Takashi Iwai
2005-08-05 9:37 ` Roman Zippel
2005-08-05 9:46 ` Arjan van de Ven
2005-08-05 9:59 ` Pekka J Enberg
2005-08-05 10:07 ` [PATCH] " Roman Zippel
2005-08-05 10:13 ` Arjan van de Ven
2005-08-05 10:32 ` Roman Zippel
2005-08-05 10:38 ` Arjan van de Ven
2005-08-05 10:56 ` Roman Zippel
2005-08-05 11:12 ` Arjan van de Ven
2005-08-06 0:40 ` Roman Zippel
2005-08-06 13:09 ` Pekka Enberg
2005-08-08 6:25 ` Jan Engelhardt
2005-08-05 17:49 ` Stephen Pollei
2005-08-05 18:16 ` Christoph Lameter
2005-08-05 18:39 ` Stephen Pollei [this message]
2005-08-05 10:15 ` Pekka J 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=feed8cdd0508051139799ff4d5@mail.gmail.com \
--to=stephen.pollei@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=pmarques@grupopie.com \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.