From: Damien Le Moal <damien.lemoal@wdc.com>
To: Benno Schulenberg <bensberg@justemail.net>, Karel Zak <kzak@redhat.com>
Cc: Shaun Tancheff <shaun@tancheff.com>,
Util-Linux <util-linux@vger.kernel.org>,
Bart Van Assche <bart.vanassche@sandisk.com>
Subject: Re: [PATCH v3] Add blkzonecmd and blkreport ZAC/ZBC drives
Date: Fri, 17 Feb 2017 09:12:29 +0900 [thread overview]
Message-ID: <ea1698c4-b055-e498-b154-d8931817bc36@wdc.com> (raw)
In-Reply-To: <1487247307.2341564.882965648.11DC77E0@webmail.messagingengine.com>
Benno,
On 2/16/17 21:15, Benno Schulenberg wrote:
>
> On Thu, Feb 16, 2017, at 11:33, Karel Zak wrote:
>> blkzone report [--zone <offset>] [--count <length>]
>> blkzone reset [--zone <offset>] [--count <length>]
>
> "blkzone --zone" feels a bit strange. I would suggest:
>
> blkzone <command> [--offset <sector>] [--count <number>]
Indeed, it is a little awkward. And to be consistent with other tools
such as blkdiscard, I would also suggest --length instead of --count.
So:
blkzone report [--offset <offset>] [--length <length>]
blkzone reset [--offset <offset>] [--length <length>]
Best regards.
--
Damien Le Moal, Ph.D.
Sr. Manager, System Software Research Group,
Western Digital Corporation
Damien.LeMoal@wdc.com
(+81) 0466-98-3593 (ext. 513593)
1 kirihara-cho, Fujisawa,
Kanagawa, 252-0888 Japan
www.wdc.com, www.hgst.com
next prev parent reply other threads:[~2017-02-17 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:32 [PATCH v3] Add blkzonecmd and blkreport ZAC/ZBC drives Shaun Tancheff
2017-02-09 12:36 ` Karel Zak
2017-02-10 3:06 ` Damien Le Moal
2017-02-10 9:59 ` Karel Zak
2017-02-16 10:33 ` Karel Zak
2017-02-16 10:41 ` Damien Le Moal
2017-02-16 12:15 ` Benno Schulenberg
2017-02-17 0:12 ` Damien Le Moal [this message]
2017-02-23 16:33 ` Karel Zak
2017-02-24 4:10 ` Damien Le Moal
2017-02-24 4:11 ` Damien Le Moal
2017-02-24 11:03 ` Karel Zak
2017-02-24 6:55 ` Damien Le Moal
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=ea1698c4-b055-e498-b154-d8931817bc36@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=bart.vanassche@sandisk.com \
--cc=bensberg@justemail.net \
--cc=kzak@redhat.com \
--cc=shaun@tancheff.com \
--cc=util-linux@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.