From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org, hch@lst.de,
linux-api@vger.kernel.org, Niklas Cassel <niklas.cassel@wdc.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCHv4 1/3] block: add zone specific block statuses
Date: Fri, 9 Oct 2020 08:29:27 -0700 [thread overview]
Message-ID: <20201009152927.GA1023921@dhcp-10-100-145-180.wdl.wdc.com> (raw)
In-Reply-To: <20200924205330.4043232-2-kbusch@kernel.org>
On Thu, Sep 24, 2020 at 01:53:28PM -0700, Keith Busch wrote:
> A zoned device with limited resources to open or activate zones may
> return an error when the host exceeds those limits. The same command may
> be successful if retried later, but the host needs to wait for specific
> zone states before it should expect a retry to succeed. Have the block
> layer provide an appropriate status for these conditions so applications
> can distinuguish this error for special handling.
Hi Jens,
Can be considered for inclusion? The series still applies cleanly to
block for-next.
next prev parent reply other threads:[~2020-10-09 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 20:53 [PATCHv4 0/3] zoned block device specific errors Keith Busch
2020-09-24 20:53 ` [PATCHv4 1/3] block: add zone specific block statuses Keith Busch
2020-10-01 21:35 ` Keith Busch
2020-10-09 15:29 ` Keith Busch [this message]
2020-10-13 17:16 ` Keith Busch
2020-10-13 19:25 ` Jens Axboe
2020-09-24 20:53 ` [PATCHv4 2/3] nvme: translate zone resource errors Keith Busch
2020-09-24 20:53 ` [PATCHv4 3/3] scsi: handle zone resources errors Keith Busch
2020-09-28 8:26 ` Johannes Thumshirn
2020-09-25 1:28 [PATCHv4 0/3] zoned block device specific errors Keith Busch
2020-09-25 1:28 ` [PATCHv4 1/3] block: add zone specific block statuses Keith Busch
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=20201009152927.GA1023921@dhcp-10-100-145-180.wdl.wdc.com \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=niklas.cassel@wdc.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).