All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: Jeff Moyer <jmoyer@redhat.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 11:02:49 +0300	[thread overview]
Message-ID: <4A3751A9.8070601@panasas.com> (raw)
In-Reply-To: <4A370B3D.4050108@ct.jp.nec.com>

On 06/16/2009 06:02 AM, Kiyoshi Ueda wrote:
> Hi Boaz, Jeff, Jens,
>>> 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.
> 

I'm convinced blk_rq_prep_clone is good for what it actually does

> Jens, what do you prefer?
> 
> Thanks,
> Kiyoshi Ueda

Thanks
Boaz

  reply	other threads:[~2009-06-16  8:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  3:10 [PATCH block#for-2.6.31] block: add request clone interface (v2) Kiyoshi Ueda
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 13:30       ` Jens Axboe
2009-06-12 14:33       ` Jeff Moyer
2009-06-15  3:31         ` Kiyoshi Ueda
2009-06-15  3:31           ` Kiyoshi Ueda
2009-06-15  9:30           ` Boaz Harrosh
2009-06-15  9:30             ` Boaz Harrosh
2009-06-16  3:02             ` Kiyoshi Ueda
2009-06-16  3:02               ` Kiyoshi Ueda
2009-06-16  8:02               ` Boaz Harrosh [this message]
2009-06-16 12:35               ` Jeff Moyer

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=4A3751A9.8070601@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=dm-devel@redhat.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=jens.axboe@oracle.com \
    --cc=jmoyer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.