From: "hch@lst.de" <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "hch@lst.de" <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Javier Gonzalez <javier.gonz@samsung.com>,
"javier@javigon.com" <javier@javigon.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"joshi.k@samsung.com" <joshi.k@samsung.com>,
"Klaus B. Jensen" <k.jensen@samsung.com>,
"Niklas.Cassel@wdc.com" <Niklas.Cassel@wdc.com>
Subject: Re: [PATCH V2] nvme: report capacity 0 for non supported ZNS SSDs
Date: Wed, 4 Nov 2020 15:29:08 +0100 [thread overview]
Message-ID: <20201104142908.GA7941@lst.de> (raw)
In-Reply-To: <23e10fd1-d20c-cf77-4dc0-dd8b0774fd7a@suse.de>
On Wed, Nov 04, 2020 at 03:26:46PM +0100, Hannes Reinecke wrote:
> I hardly dare to mention bsg here; but the is pretty similar to what it set
> out to do ...
Except that:
a) we created a complete mess with bsg by overloading the scsi ioctls
with some of the transport stuff.
b) bsg would not work with existing tools. A character device that
accepts the same ioctl will just work.
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"Niklas.Cassel@wdc.com" <Niklas.Cassel@wdc.com>,
"javier@javigon.com" <javier@javigon.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"joshi.k@samsung.com" <joshi.k@samsung.com>,
"Klaus B. Jensen" <k.jensen@samsung.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Keith Busch <kbusch@kernel.org>,
Javier Gonzalez <javier.gonz@samsung.com>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH V2] nvme: report capacity 0 for non supported ZNS SSDs
Date: Wed, 4 Nov 2020 15:29:08 +0100 [thread overview]
Message-ID: <20201104142908.GA7941@lst.de> (raw)
In-Reply-To: <23e10fd1-d20c-cf77-4dc0-dd8b0774fd7a@suse.de>
On Wed, Nov 04, 2020 at 03:26:46PM +0100, Hannes Reinecke wrote:
> I hardly dare to mention bsg here; but the is pretty similar to what it set
> out to do ...
Except that:
a) we created a complete mess with bsg by overloading the scsi ioctls
with some of the transport stuff.
b) bsg would not work with existing tools. A character device that
accepts the same ioctl will just work.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-11-04 14:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201102161505eucas1p19415e34eb0b14c7eca5a2c648569cf1e@eucas1p1.samsung.com>
[not found] ` <0916865d50c640e3aa95dc542f3986b9@CAMSVWEXC01.scsc.local>
2020-11-02 16:30 ` [PATCH V2] nvme: report capacity 0 for non supported ZNS SSDs Niklas Cassel
2020-11-02 16:30 ` Niklas Cassel
2020-11-02 21:25 ` Javier Gonzalez
2020-11-02 21:25 ` Javier Gonzalez
2020-11-02 18:08 ` [PATCH V2] " hch
2020-11-02 18:08 ` hch
2020-11-02 18:33 ` Keith Busch
2020-11-02 18:33 ` Keith Busch
2020-11-02 18:58 ` hch
2020-11-02 18:58 ` hch
2020-11-02 21:24 ` Javier Gonzalez
2020-11-02 21:24 ` Javier Gonzalez
2020-11-03 9:06 ` hch
2020-11-03 9:06 ` hch
2020-11-03 14:10 ` Javier Gonzalez
2020-11-03 14:10 ` Javier Gonzalez
2020-11-03 15:26 ` hch
2020-11-03 15:26 ` hch
2020-11-03 15:54 ` Javier Gonzalez
2020-11-03 15:54 ` Javier Gonzalez
2020-11-04 14:26 ` [PATCH V2] " Hannes Reinecke
2020-11-04 14:26 ` Hannes Reinecke
2020-11-04 14:29 ` hch [this message]
2020-11-04 14:29 ` hch
2020-11-04 14:46 ` Hannes Reinecke
2020-11-04 14:46 ` Hannes Reinecke
2020-11-05 7:37 ` hch
2020-11-05 7:37 ` hch
2020-11-05 7:42 ` Hannes Reinecke
2020-11-05 7:42 ` Hannes Reinecke
2020-11-02 13:22 Javier González
2020-11-02 13:22 ` Javier González
2020-11-02 15:44 ` Keith Busch
2020-11-02 15:44 ` 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=20201104142908.GA7941@lst.de \
--to=hch@lst.de \
--cc=Niklas.Cassel@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=javier.gonz@samsung.com \
--cc=javier@javigon.com \
--cc=joshi.k@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.