From: Coly Li <colyli@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, damien.lemoal@wdc.com,
hare@suse.com, axboe@kernel.dk, linux-bcache@vger.kernel.org,
kbusch@kernel.org, Hannes Reinecke <hare@suse.de>,
Jens Axboe <axboe@fb.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Shaun Tancheff <shaun.tancheff@seagate.com>
Subject: Re: [RFC PATCH v2 1/4] block: change REQ_OP_ZONE_RESET from 6 to 13
Date: Sat, 16 May 2020 20:44:45 +0800 [thread overview]
Message-ID: <fc0fd3c9-ea46-7c62-2a57-abd64e79cd08@suse.de> (raw)
In-Reply-To: <20200516123801.GB13448@lst.de>
On 2020/5/16 20:38, Christoph Hellwig wrote:
> On Sat, May 16, 2020 at 11:54:31AM +0800, Coly Li wrote:
>> For a zoned device, e.g. host managed SMR hard drive, REQ_OP_ZONE_RESET
>> is to reset the LBA of a zone's write pointer back to the start LBA of
>> this zone. After the write point is reset, all previously stored data
>> in this zone is invalid and unaccessible anymore. Therefore, this op
>> code changes on disk data, belongs to a WRITE request op code.
>>
>> Current REQ_OP_ZONE_RESET is defined as number 6, but the convention of
>> the op code is, READ requests are even numbers, and WRITE requests are
>> odd numbers. See how op_is_write defined,
>
> The convention is all about data transfer, and zone reset does not
> transfer any data.
>
Yes you are right, just like REQ_OP_DISCARD which does not transfer any
data but changes the data on device. If the request changes the stored
data, it does transfer data.
This is why in patch "block: set bi_size to REQ_OP_ZONE_RESET bio" I set
bi_size to the REQ_OP_ZONE_RESET and REQ_OP_ZONE_RESET_ALL bios.
Coly Li
next prev parent reply other threads:[~2020-05-16 12:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 3:54 [RFC PATCH v2 0/4] block layer change necessary for bcache zoned device support Coly Li
2020-05-16 3:54 ` [RFC PATCH v2 1/4] block: change REQ_OP_ZONE_RESET from 6 to 13 Coly Li
2020-05-16 4:06 ` Chaitanya Kulkarni
2020-05-16 9:33 ` Coly Li
2020-05-16 12:38 ` Christoph Hellwig
2020-05-16 12:44 ` Coly Li [this message]
2020-05-16 12:50 ` Christoph Hellwig
2020-05-16 13:05 ` Coly Li
2020-05-16 15:36 ` Christoph Hellwig
2020-05-17 5:30 ` Coly Li
2020-05-18 6:53 ` Hannes Reinecke
2020-05-18 6:56 ` Damien Le Moal
2020-05-18 0:33 ` Damien Le Moal
2020-05-18 5:09 ` Chaitanya Kulkarni
2020-05-16 3:54 ` [RFC PATCH v2 2/4] block: block: change REQ_OP_ZONE_RESET_ALL from 8 to 15 Coly Li
2020-05-18 0:36 ` Damien Le Moal
2020-05-16 3:54 ` [RFC PATCH v2 3/4] block: remove queue_is_mq restriction from blk_revalidate_disk_zones() Coly Li
2020-05-16 12:40 ` Christoph Hellwig
2020-05-16 13:13 ` Coly Li
2020-05-16 15:35 ` Christoph Hellwig
2020-05-18 1:07 ` Damien Le Moal
2020-05-18 0:39 ` Damien Le Moal
2020-05-16 3:54 ` [RFC PATCH v2 4/4] block: set bi_size to REQ_OP_ZONE_RESET bio Coly Li
2020-05-16 12:53 ` Christoph Hellwig
2020-05-18 0:59 ` Damien Le Moal
2020-05-18 2:32 ` Coly Li
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=fc0fd3c9-ea46-7c62-2a57-abd64e79cd08@suse.de \
--to=colyli@suse.de \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=shaun.tancheff@seagate.com \
/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.