public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Paulo Marques <pmarques@grupopie.com>
Cc: "Pekka Enberg" <penberg@gmail.com>,
	"Roland Dreier" <roland@topspin.com>,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	LKML <linux-kernel@vger.kernel.org>,
	penberg@cs.helsinki.fi, "Jesper Juhl" <juhl-lkml@dif.dk>
Subject: Re: RFC: turn kmalloc+memset(,0,) into kcalloc
Date: Thu, 7 Apr 2005 19:54:17 -0400	[thread overview]
Message-ID: <360495f04d557922068b477d7e149778@mac.com> (raw)
In-Reply-To: <42540560.2000205@grupopie.com>

On Apr 06, 2005, at 11:50, Paulo Marques wrote:
> kzalloc it is, then.
>
> [...]
>
> So we gain 8kB on the uncompressed image and 1347 bytes on the 
> compressed one. This was just a dumb test and actual results might be 
> better due to smarter human cleanups.
>
> Not a spectacular gain per se, but the increase in code readability is 
> still worth it, IMHO.

Perhaps this could eventually be modified to draw from a prezeroed 
block of
memory, similar to the current code for doing the same thing for 
userspace.
It probably wouldn't give much performance gain, especially since it's 
not
used for large blocks or large numbers of small objects (As you would 
use a
slabcache for those), but it might help a bit.  Of course, the code 
would
need to fall back quickly if such an allocation would be messy or 
expensive
for any reason.

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r  
!y?(-)
------END GEEK CODE BLOCK------



  reply	other threads:[~2005-04-07 23:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 16:26 RFC: turn kmalloc+memset(,0,) into kcalloc Paulo Marques
2005-04-05 18:00 ` Jörn Engel
2005-04-06 12:09   ` Denis Vlasenko
2005-04-05 18:54 ` Jesper Juhl
2005-04-05 19:20   ` Roland Dreier
2005-04-05 20:01     ` Jesper Juhl
2005-04-06 11:28       ` Jörn Engel
2005-04-06 12:15         ` Paulo Marques
2005-04-06 13:10           ` Pekka Enberg
2005-04-06 15:50             ` Paulo Marques
2005-04-07 23:54               ` Kyle Moffett [this message]
2005-04-09  2:11         ` Jesper Juhl
2005-04-07 21:47 ` Adrian Bunk
2005-04-08 12:38   ` Paulo Marques
2005-04-08 13:00     ` Adrian Bunk
2005-04-08 13:20       ` Jörn Engel
2005-04-08 13:29         ` Adrian Bunk
2005-04-08 16:24       ` Paulo Marques
2005-04-08 19:43         ` Adrian Bunk
2005-04-08 19:49           ` Randy.Dunlap
2005-04-08 13:00     ` stack checking (was: Re: RFC: turn kmalloc+memset(,0,) into kcalloc) Jörn Engel
2005-04-09 14:19     ` RFC: turn kmalloc+memset(,0,) into kcalloc Paul Jackson

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=360495f04d557922068b477d7e149778@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=penberg@gmail.com \
    --cc=pmarques@grupopie.com \
    --cc=roland@topspin.com \
    /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