From: Joe Perches <joe@perches.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
james.smart@broadcom.com, ram.vegesna@broadcom.com,
jejb@linux.ibm.com, martin.petersen@oracle.com, hare@suse.de,
dwagner@suse.de
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scsi: elx: efct: Avoid a useless memset
Date: Thu, 09 Dec 2021 14:29:51 -0800 [thread overview]
Message-ID: <eb1f435113e1f42de2521e12fd0d588fca673735.camel@perches.com> (raw)
In-Reply-To: <52c4bc82-f8eb-c884-dfd8-2579f6632517@wanadoo.fr>
On Thu, 2021-12-09 at 23:19 +0100, Christophe JAILLET wrote:
> Le 09/12/2021 à 22:57, Joe Perches a écrit :
> > On Thu, 2021-12-09 at 22:51 +0100, Christophe JAILLET wrote:
> > > 'io->sgl' is kzalloced just a few lines above. There is no need to memset
> > > it another time.
> >
> > Better to use kcalloc as well and delete the memset
>
> Sure, thanks for spotting it Joe.
>
> Should a clean v2 be sent or the patch in your reply is enough?
> As your proposal is better than mine, if a v2 is needed, can you do it?
Hi Christophe.
I just wondered about the multiplication in the memset.
You are the patch submitter and noticed it in the first place.
If needed I think you should do it.
cheers, Joe
> > diff --git a/drivers/scsi/elx/efct/efct_io.c b/drivers/scsi/elx/efct/efct_io.c
[]
> > @@ -56,13 +56,12 @@ efct_io_pool_create(struct efct *efct, u32 num_sgl)
> > }
> >
> > /* Allocate SGL */
> > - io->sgl = kzalloc(sizeof(*io->sgl) * num_sgl, GFP_KERNEL);
> > + io->sgl = kcalloc(num_sgl, sizeof(*io->sgl), GFP_KERNEL);
> > if (!io->sgl) {
> > efct_io_pool_free(io_pool);
> > return NULL;
> > }
> >
> > - memset(io->sgl, 0, sizeof(*io->sgl) * num_sgl);
> > io->sgl_allocated = num_sgl;
> > io->sgl_count = 0;
> >
prev parent reply other threads:[~2021-12-09 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 21:51 Christophe JAILLET
2021-12-09 21:57 ` Joe Perches
2021-12-09 22:19 ` Christophe JAILLET
2021-12-09 22:29 ` Joe Perches [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=eb1f435113e1f42de2521e12fd0d588fca673735.camel@perches.com \
--to=joe@perches.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ram.vegesna@broadcom.com \
--cc=target-devel@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
all inboxes | Powered by JetHome®