From: Christoph Lameter <clameter@sgi.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
jsipek@fsl.cs.sunysb.edu, unionfs@filesystems.org,
bunk@stusta.de, hooanon05@yahoo.co.jp
Subject: Re: [PATCH 1/3] slab: introduce krealloc
Date: Wed, 21 Feb 2007 09:53:15 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702210951580.24344@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702211003290.8172@sbz-30.cs.Helsinki.FI>
On Wed, 21 Feb 2007, Pekka J Enberg wrote:
> +void *krealloc(const void *p, size_t new_size, gfp_t flags)
> +{
> + void *ret;
> +
> + if (unlikely(!p))
> + return kmalloc_track_caller(new_size, flags);
> +
> + if (unlikely(!new_size)) {
> + kfree(p);
> + return NULL;
> + }
> +
> + ret = kmalloc_track_caller(new_size, flags);
> + if (!ret)
> + return NULL;
> +
> + memcpy(ret, p, min(new_size, ksize(p)));
> + kfree(p);
> + return ret;
> +}
> +EXPORT_SYMBOL(krealloc);
Well could you check ksize for the old object first and if ksize <= new
size then just skip the copy? I think this may allow you
to get rid of the ksize callers.
next prev parent reply other threads:[~2007-02-21 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 8:06 Pekka J Enberg
2007-02-21 9:24 ` Arjan van de Ven
2007-02-21 9:33 ` Pekka Enberg
2007-02-21 9:36 ` Arjan van de Ven
2007-02-21 17:51 ` Christoph Lameter
2007-02-21 17:53 ` Christoph Lameter [this message]
2007-02-21 18:21 ` Pekka Enberg
2007-02-21 18:27 ` Christoph Lameter
2007-02-21 18:37 ` Pekka Enberg
2007-02-21 18:48 ` Christoph Lameter
2007-02-21 19:19 ` Pekka Enberg
2007-02-21 19:22 ` Christoph Lameter
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=Pine.LNX.4.64.0702210951580.24344@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=hooanon05@yahoo.co.jp \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=unionfs@filesystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®