From: Zheng Liu <gnehzuil.liu@gmail.com>
To: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Cc: Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PATCH] jbd: use kmem_cache_zalloc instead of kmem_cache_alloc/memset
Date: Thu, 25 Apr 2013 18:12:49 +0800 [thread overview]
Message-ID: <20130425101249.GA16770@gmail.com> (raw)
In-Reply-To: <1365769446-22034-1-git-send-email-wenqing.lz@taobao.com>
On Fri, Apr 12, 2013 at 08:24:06PM +0800, Zheng Liu wrote:
> From: Zheng Liu <wenqing.lz@taobao.com>
>
> Now jbd_alloc_handle is only called by new_handle. So this commit
> uses kmem_cache_zalloc instead of kmem_cache_alloc/memset.
>
> Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
Hi Jan,
Sorry, I forgot to Cc you. Could you please take a look at this patch?
Thanks,
- Zheng
> ---
> fs/jbd/transaction.c | 1 -
> include/linux/jbd.h | 2 +-
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/jbd/transaction.c b/fs/jbd/transaction.c
> index 071d690..e3e255c 100644
> --- a/fs/jbd/transaction.c
> +++ b/fs/jbd/transaction.c
> @@ -245,7 +245,6 @@ static handle_t *new_handle(int nblocks)
> handle_t *handle = jbd_alloc_handle(GFP_NOFS);
> if (!handle)
> return NULL;
> - memset(handle, 0, sizeof(*handle));
> handle->h_buffer_credits = nblocks;
> handle->h_ref = 1;
>
> diff --git a/include/linux/jbd.h b/include/linux/jbd.h
> index c8f3297..7e0b622 100644
> --- a/include/linux/jbd.h
> +++ b/include/linux/jbd.h
> @@ -887,7 +887,7 @@ extern struct kmem_cache *jbd_handle_cache;
>
> static inline handle_t *jbd_alloc_handle(gfp_t gfp_flags)
> {
> - return kmem_cache_alloc(jbd_handle_cache, gfp_flags);
> + return kmem_cache_zalloc(jbd_handle_cache, gfp_flags);
> }
>
> static inline void jbd_free_handle(handle_t *handle)
> --
> 1.7.12.rc2.18.g61b472e
>
next prev parent reply other threads:[~2013-04-25 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 12:24 [PATCH] jbd: use kmem_cache_zalloc instead of kmem_cache_alloc/memset Zheng Liu
2013-04-25 10:12 ` Zheng Liu [this message]
2013-04-25 13:27 ` Jan Kara
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=20130425101249.GA16770@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.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