From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] scsi: Implement 'ZBC' device type
Date: Mon, 2 Jun 2014 02:20:53 -0700 [thread overview]
Message-ID: <20140602092053.GD32301@infradead.org> (raw)
In-Reply-To: <538C39EB.90109@suse.de>
On Mon, Jun 02, 2014 at 10:46:35AM +0200, Hannes Reinecke wrote:
> >But I'm uneasy with adding anything like this for now, for one the specs
> >aren't even anywhere close to done, and second attaching ZBC devices
> >in general doesn't sound like a very smart idea, we really need a
> >strategy for the sequential required zones first.
> >
> In theory, yes.
>
> In practice, however, ZAC drives will show up a normal ATA devices
> without that patch. Which is leading to even more trouble.
> So with this patch we're at least signalling to the user that
> something odd might happen.
So how about we drop the sd.c changes so that no ULD gets attached,
and keep the rest with the review comments addressed? That way we
don't accidentally attach a ZBC/ZAC disk, but do get proper diagnostics
and can even use SG_IO with the experimental ZBC or ZAC commands.
next prev parent reply other threads:[~2014-06-02 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 7:01 [PATCH 0/3] Initial SMR drive support Hannes Reinecke
2014-06-02 7:01 ` [PATCH 1/3] libata: consolidate ata_dev_classify() Hannes Reinecke
2014-06-02 9:16 ` Christoph Hellwig
2014-06-02 7:01 ` [PATCH 2/3] libata: Implement ATA_DEV_ZAC Hannes Reinecke
2014-06-02 9:17 ` Christoph Hellwig
2014-06-14 6:37 ` Hannes Reinecke
2014-06-02 7:01 ` [PATCH 3/3] scsi: Implement 'ZBC' device type Hannes Reinecke
2014-06-02 8:39 ` Christoph Hellwig
2014-06-02 8:46 ` Hannes Reinecke
2014-06-02 9:20 ` Christoph Hellwig [this message]
2014-06-02 9:19 ` Christoph Hellwig
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=20140602092053.GD32301@infradead.org \
--to=hch@infradead.org \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).