diff for duplicates of <20160816234508.GA12482@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index fe65659..40cd204 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,18 +1,18 @@ -On Tue, Aug 16, 2016@01:45:03PM -0700, J Freyensee wrote: -> On Mon, 2016-08-15@22:41 -0300, Helen Koike wrote: -> > ? struct nvmf_connect_command connect; -> > ? struct nvmf_property_set_command prop_set; -> > ? struct nvmf_property_get_command prop_get; +On Tue, Aug 16, 2016 at 01:45:03PM -0700, J Freyensee wrote: +> On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote: +> > struct nvmf_connect_command connect; +> > struct nvmf_property_set_command prop_set; +> > struct nvmf_property_get_command prop_get; > > + struct nvme_doorbell_memory doorbell_memory; -> > ? }; -> > ?}; +> > }; +> > }; > > This looks like a new NVMe command being introduced, not found in the > latest NVMe specs (NVMe 1.2.1 spec or NVMe-over-Fabrics 1.0 spec)? > > This is a big NACK, the command needs to be part of the NVMe standard > before adding it to the NVMe code base (this is exactly how NVMe-over- -> Fabrics standard got implemented). ?I would bring your proposal to +> Fabrics standard got implemented). I would bring your proposal to > nvmexpress.org. While this is an approved TPAR up for consideration soon, I don't think we diff --git a/a/content_digest b/N1/content_digest index c2c05db..b525386 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,26 +2,43 @@ "ref\0cover.1471308889.git.helen.koike@collabora.co.uk\0" "ref\0c738f3d3c14907a9074a40b1658461e008fbed9e.1471308889.git.helen.koike@collabora.co.uk\0" "ref\01471380303.21107.38.camel@linux.intel.com\0" - "From\0keith.busch@intel.com (Keith Busch)\0" - "Subject\0[PATCH v3 RFC 2/2] nvme: improve performance for virtual NVMe devices\0" + "From\0Keith Busch <keith.busch@intel.com>\0" + "Subject\0Re: [PATCH v3 RFC 2/2] nvme: improve performance for virtual NVMe devices\0" "Date\0Tue, 16 Aug 2016 23:45:08 +0000\0" + "To\0J Freyensee <james_p_freyensee@linux.intel.com>\0" + "Cc\0Helen Koike <helen.koike@collabora.co.uk>" + hch@infradead.org + mlin@kernel.org + fes@google.com + rlnelson@google.com + axboe@fb.com + digitaleric@google.com + tytso@mit.edu + mikew@google.com + monish@google.com + open list <linux-kernel@vger.kernel.org> + open list:NVM EXPRESS DRIVER <linux-nvme@lists.infradead.org> + Huffman + Amber <amber.huffman@intel.com> + Minturn + " Dave B <dave.b.minturn@intel.com>\0" "\00:1\0" "b\0" - "On Tue, Aug 16, 2016@01:45:03PM -0700, J Freyensee wrote:\n" - "> On Mon, 2016-08-15@22:41 -0300, Helen Koike wrote:\n" - "> > ?\t\tstruct nvmf_connect_command connect;\n" - "> > ?\t\tstruct nvmf_property_set_command prop_set;\n" - "> > ?\t\tstruct nvmf_property_get_command prop_get;\n" + "On Tue, Aug 16, 2016 at 01:45:03PM -0700, J Freyensee wrote:\n" + "> On Mon, 2016-08-15 at 22:41 -0300, Helen Koike wrote:\n" + "> > \302\240\t\tstruct nvmf_connect_command connect;\n" + "> > \302\240\t\tstruct nvmf_property_set_command prop_set;\n" + "> > \302\240\t\tstruct nvmf_property_get_command prop_get;\n" "> > +\t\tstruct nvme_doorbell_memory doorbell_memory;\n" - "> > ?\t};\n" - "> > ?};\n" + "> > \302\240\t};\n" + "> > \302\240};\n" "> \n" "> This looks like a new NVMe command being introduced, not found in the\n" "> latest NVMe specs (NVMe 1.2.1 spec or NVMe-over-Fabrics 1.0 spec)?\n" "> \n" "> This is a big NACK, the command needs to be part of the NVMe standard\n" "> before adding it to the NVMe code base (this is exactly how NVMe-over-\n" - "> Fabrics standard got implemented). ?I would bring your proposal to\n" + "> Fabrics standard got implemented). \302\240I would bring your proposal to\n" "> nvmexpress.org.\n" "\n" "While this is an approved TPAR up for consideration soon, I don't think we\n" @@ -32,4 +49,4 @@ "done publicly until the spec is also public. The proposal originated\n" from a public RFC, though, so it's not a secret. -7f0d17cf2b05497ef53cc28acc24d83f797cdebba392a6443e18b487f87525d9 +65b8c08872bc8c2304a891ad4b0e16611c1315e567ed15ff9377e1ce3c12328f
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.