public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: fanchaoting <fanchaoting@cn.fujitsu.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: don't  calculate mem's size in loop every time
Date: Fri, 12 Apr 2013 10:48:04 -0400	[thread overview]
Message-ID: <20130412144804.GJ7081@fieldses.org> (raw)
In-Reply-To: <5163AF52.2080303@cn.fujitsu.com>

On Tue, Apr 09, 2013 at 02:04:02PM +0800, fanchaoting wrote:
> 
>  Signed-off-by: fanchaoting <fanchaoting@cn.fujitsu.com>

Thanks, this makes sense, but meanwhile I've been rewriting that
code--now pushed out to my for-3.10 branch.  Let me know if you see
anything that looks wrong there.

--b.

> ---
>  fs/nfsd/nfs4state.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 2e27430..df3e3fd 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -716,8 +716,8 @@ static struct nfsd4_session *__alloc_session(int slotsize, int numslots)
>  	if (!new)
>  		return NULL;
>  	/* allocate each struct nfsd4_slot and data cache in one piece */
> +	mem = sizeof(struct nfsd4_slot) + slotsize;
>  	for (i = 0; i < numslots; i++) {
> -		mem = sizeof(struct nfsd4_slot) + slotsize;
>  		new->se_slots[i] = kzalloc(mem, GFP_KERNEL);
>  		if (!new->se_slots[i])
>  			goto out_free;
> -- 
> 1.7.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-04-12 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  6:04 [PATCH] nfsd: don't calculate mem's size in loop every time fanchaoting
2013-04-12 14:48 ` bfields [this message]

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=20130412144804.GJ7081@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=fanchaoting@cn.fujitsu.com \
    --cc=linux-nfs@vger.kernel.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