From: Christoph Hellwig <hch@infradead.org>
To: Shaun Tancheff <shaun@tancheff.com>
Cc: linux-ide@vger.kernel.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Jeff Layton <jlayton@poochiereds.net>,
"J . Bruce Fields" <bfields@fieldses.org>,
Shaun Tancheff <shaun.tancheff@seagate.com>
Subject: Re: [PATCH v3 1/3] Add bio/request flags for using ZBC/ZAC commands
Date: Mon, 13 Jun 2016 01:01:07 -0700 [thread overview]
Message-ID: <20160613080107.GA26544@infradead.org> (raw)
In-Reply-To: <1465542833-26828-1-git-send-email-shaun@tancheff.com>
On Fri, Jun 10, 2016 at 02:13:53AM -0500, Shaun Tancheff wrote:
> T10 ZBC and T13 ZAC specify operations for Zoned devices.
>
> To be able to access the zone information and open and close zones
> adding flags for the report zones command (REQ_REPORT_ZONES) and for
> Open and Close zone (REQ_OPEN_ZONE and REQ_CLOSE_ZONE) can be added
> for use by struct bio's bi_rw and by struct request's cmd_flags.
These need to be new operations, e.g. they should be in the REQ_OP_*
enum. And please use a separate opcode for each actual operation.
prev parent reply other threads:[~2016-06-13 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 7:10 [PATCH v3 0/3] Block layer support ZAC/ZBC commands Shaun Tancheff
2016-06-10 7:10 ` [PATCH v3 1/3] Add bio/request flags for using ZBC/ZAC commands Shaun Tancheff
2016-06-10 7:10 ` [PATCH v3 2/3] Add ioctl to issue ZBC/ZAC commands via block layer Shaun Tancheff
2016-06-10 7:10 ` [PATCH v3 3/3] Add ata pass-through path for ZAC commands Shaun Tancheff
2016-06-10 7:19 ` Hannes Reinecke
2016-06-10 7:28 ` Shaun Tancheff
2016-06-10 7:13 ` [PATCH v3 1/3] Add bio/request flags for using ZBC/ZAC commands Shaun Tancheff
2016-06-13 8:01 ` Christoph Hellwig [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=20160613080107.GA26544@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bfields@fieldses.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jlayton@poochiereds.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun.tancheff@seagate.com \
--cc=shaun@tancheff.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).