From: Jeff Moyer <jmoyer@redhat.com>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>,
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Subject: Re: [PATCH block#for-2.6.31] block: add request clone interface (v2)
Date: Tue, 16 Jun 2009 08:35:53 -0400 [thread overview]
Message-ID: <x49zlc8cq52.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4A370B3D.4050108@ct.jp.nec.com> (Kiyoshi Ueda's message of "Tue, 16 Jun 2009 12:02:21 +0900")
Kiyoshi Ueda <k-ueda@ct.jp.nec.com> writes:
> Hi Boaz, Jeff, Jens,
>
> Thank you for your ideas.
> It's time to decide now? Please see below.
>
> On 2009/06/15 18:30 +0900, Boaz Harrosh wrote:
>> > On 06/15/2009 06:31 AM, Kiyoshi Ueda wrote:
>>> >> On 06/12/2009 11:33 PM +0900, Jeff Moyer wrote:
>>>> >>> Jens Axboe <jens.axboe@oracle.com> writes:
>>>>> >>>> On Thu, Jun 11 2009, Jeff Moyer wrote:
>>>>>> >>>>> Jens Axboe <jens.axboe@oracle.com> writes:
>>>>>> >>>>> Is blk_rq_unprep_clone really the best name?
>>>>>> >>>>> ^^^^^^
>>>>> >>>> Probably not, but I'm not very good at coming up with elegant names.
>>>>> >>>> Your email should have included a new suggestion :-)
>>>> >>> Fair enough. ;)
>>>> >>>
>>>>> >>>> - blk_rq_unprep_clone(struct request *clone)
>>>>> >>>> * Frees cloned bios from the clone request.
>>>> >>> Why not blk_rq_free_clone?
>>> >> Because the 'clone' is not freed in this interface.
>>> >> This interface frees only bios in the 'clone'.
>>> >> Allocating/freeing the 'clone' are the caller's work, since
>>> >> only the caller knows how to allocate/free it.
>>> >>
>>> >> 'prep' after 'alloc' and 'unprep' before 'free' is symmetric
>>> >> and I feel a good candidate for my request-stacking driver,
>>> >> so I chose it.
>> >
>> > I'm not a native English speaker as well, so I'm fine
>> > with blk_rq_{prep,unprep}_clone. But maybe the English
>> > people don't like it?
>> >
>> > Perhaps
>> > blk_rq_{clone,declone} or blk_rq_{clone,declone}_bios
>> >
>> > (Both unclone and declone are found on the net but are not
>> > found in the free dictionary)
>
> I had a feeling that blk_rq_{clone,declone} allocates/frees
> the clone request inside the interfaces like bio_clone(), so
> I didn't take such namings.
> And, the clone setup interface may not only make bio clones
> but also do something else (for other request members), so
> I didn't add any 'bio' namings to the interfaces.
>
> Jens, what do you prefer?
I can live with it as it stands. prep/unprep at least has some
symmetry.
Cheers,
Jeff
prev parent reply other threads:[~2009-06-16 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 3:10 Kiyoshi Ueda
2009-06-11 11:09 ` Jens Axboe
2009-06-11 12:53 ` Jeff Moyer
2009-06-12 13:30 ` Jens Axboe
2009-06-12 14:33 ` Jeff Moyer
2009-06-15 3:31 ` Kiyoshi Ueda
2009-06-15 9:30 ` Boaz Harrosh
2009-06-16 3:02 ` Kiyoshi Ueda
2009-06-16 8:02 ` Boaz Harrosh
2009-06-16 12:35 ` Jeff Moyer [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=x49zlc8cq52.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=bharrosh@panasas.com \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@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®