From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [PATCH 1/2] consolidate command allocation in a single place
Date: Thu, 13 Mar 2008 12:15:41 -0500 [thread overview]
Message-ID: <1205428542.2893.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20080313170924.GK613@parisc-linux.org>
On Thu, 2008-03-13 at 11:09 -0600, Matthew Wilcox wrote:
> On Thu, Mar 13, 2008 at 11:53:11AM -0500, James Bottomley wrote:
> > Since the way we allocate commands with a separate sense buffer is
> > getting complicated, we should isolate setup and teardown to a single
> > routine so that if it gets even more complex, there's only one place
> > in the code that needs to be altered.
>
> > +static struct scsi_cmnd *
> > +scsi_get_command_from_pool(struct scsi_host_cmd_pool *pool, gfp_t gfp_mask)
> > +static void
> > +scsi_put_command_to_pool(struct scsi_host_cmd_pool *pool,
> > + struct scsi_cmnd *cmd)
>
> The names are a bit clunky ... 'put command to pool'? How about
> alloc/free instead of get/put? or:
>
> scsi_pool_alloc_command(struct scsi_host_cmd_pool *pool, gfp_t gfp_mask)
> scsi_pool_free_command(struct scsi_host_cmd_pool *pool, struct scsi_cmnd *cmd)
>
> or even:
>
> scsi_command_pool_alloc(struct scsi_host_cmd_pool *pool, gfp_t gfp_mask)
> scsi_command_pool_free(struct scsi_host_cmd_pool *pool, struct scsi_cmnd *cmd)
>
> (i also wouldn't object to use 'cmnd' or 'cmd' in place of 'command').
Yes, but it's following the naming convention in the file. OK, I don't
like it as well, that's why the new functions in the following patch
have alloc/free.
James
next prev parent reply other threads:[~2008-03-13 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 16:53 [PATCH 1/2] consolidate command allocation in a single place James Bottomley
2008-03-13 17:09 ` Matthew Wilcox
2008-03-13 17:15 ` James Bottomley [this message]
2008-03-17 18:25 ` James Bottomley
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=1205428542.2893.26.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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