From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>,
"Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
Boaz Harrosh <bharrosh@panasas.com>,
k-ueda@ct.jp.nec.com
Subject: Re: [PATCH block#for-2.6.31] block: add request clone interface
Date: Wed, 10 Jun 2009 11:15:29 +0900 [thread overview]
Message-ID: <4A2F1741.8090100@ct.jp.nec.com> (raw)
In-Reply-To: <20090609180344.GQ11363@kernel.dk>
Hi Jens,
On 06/10/2009 03:03 AM +0900, Jens Axboe wrote:
> On Tue, Jun 09 2009, Kiyoshi Ueda wrote:
>> Hi Jens,
>>
>> +/*
>> + * Copy request information of the original request to the clone request.
>> + */
>> +static void __blk_rq_prep_clone(struct request *dst, struct request *src)
>> +{
>> + dst->cpu = src->cpu;
>> + dst->cmd_flags = (rq_data_dir(src) | REQ_NOMERGE);
>> + dst->cmd_type = src->cmd_type;
>> + dst->__sector = blk_rq_pos(src);
>> + dst->__data_len = blk_rq_bytes(src);
>> + dst->nr_phys_segments = src->nr_phys_segments;
>> + dst->ioprio = src->ioprio;
>> + dst->buffer = src->buffer;
>> + dst->cmd_len = src->cmd_len;
>> + dst->cmd = src->cmd;
>
> Are you making sure that 'src' always exists while 'dst' is alive?
Yes.
Request-based dm is the owner of 'src' (original) and
it never frees 'src' until the 'dst' (clone) are completed.
I avoided deep-copying __cmd/buffer/sense as it's costly
(additional allocation and memcpy).
And I don't think there are any needs for that.
But if anyone really wants that even with the copying cost,
please speak up.
Thanks,
Kiyoshi Ueda
next prev parent reply other threads:[~2009-06-10 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 7:51 [PATCH block#for-2.6.31] block: add request clone interface Kiyoshi Ueda
2009-06-09 13:49 ` Boaz Harrosh
2009-06-09 18:03 ` Jens Axboe
2009-06-10 2:15 ` Kiyoshi Ueda [this message]
2009-06-10 4:30 ` Jens Axboe
2009-06-11 3:17 ` Kiyoshi Ueda
2009-06-11 9:20 ` Jens Axboe
2009-06-10 7:55 ` Boaz Harrosh
2009-06-11 3:18 ` Kiyoshi Ueda
2009-06-17 9:19 ` Tejun Heo
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=4A2F1741.8090100@ct.jp.nec.com \
--to=k-ueda@ct.jp.nec.com \
--cc=bharrosh@panasas.com \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jens.axboe@oracle.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