diff for duplicates of <1502115492.2841.20.camel@HansenPartnership.com> diff --git a/a/1.txt b/N1/1.txt index 0c0955c..7e8c9d5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,20 +1,20 @@ -On Mon, 2017-08-07@19:26 +0530, Kashyap Desai wrote: +On Mon, 2017-08-07 at 19:26 +0530, Kashyap Desai wrote: > > > > -----Original Message----- -> > From: James Bottomley [mailto:James.Bottomley at HansenPartnership.com +> > From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com > > ] > > Sent: Saturday, August 05, 2017 8:12 PM > > To: Christoph Hellwig; Hannes Reinecke -> > Cc: Suganath Prabu S; martin.petersen at oracle.com; linux- -> > scsi at vger.kernel.org; Sathya.Prakash at broadcom.com; -> > kashyap.desai at broadcom.com; linux-kernel at vger.kernel.org; -> > chaitra.basappa at broadcom.com; sreekanth.reddy at broadcom.com; linux- -> > nvme at lists.infradead.org +> > Cc: Suganath Prabu S; martin.petersen@oracle.com; linux- +> > scsi@vger.kernel.org; Sathya.Prakash@broadcom.com; +> > kashyap.desai@broadcom.com; linux-kernel@vger.kernel.org; +> > chaitra.basappa@broadcom.com; sreekanth.reddy@broadcom.com; linux- +> > nvme@lists.infradead.org > > Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support: > > -> > On Sat, 2017-08-05@06:53 -0700, Christoph Hellwig wrote: +> > On Sat, 2017-08-05 at 06:53 -0700, Christoph Hellwig wrote: > > > -> > > On Wed, Aug 02, 2017@10:14:40AM +0200, Hannes Reinecke wrote: +> > > On Wed, Aug 02, 2017 at 10:14:40AM +0200, Hannes Reinecke wrote: > > > > > > > > > > > > I'm not happy with this approach. @@ -31,7 +31,7 @@ On Mon, 2017-08-07@19:26 +0530, Kashyap Desai wrote: > > > > other > > > > NVMe HBA. > > > -> > > That doesn't make any sense.??The devices behind the mpt adapter +> > > That doesn't make any sense. The devices behind the mpt adapter > > > don't > > > look like NVMe devices at all for the hosts - there are no NVMe > > > commands or queues involved at all, they hide behind the same @@ -50,14 +50,14 @@ On Mon, 2017-08-07@19:26 +0530, Kashyap Desai wrote: > > sysfs > > files as everything else for SAS devices. > -> ?Ventura generation of controllers are adding connectivity of NVME -> ?drives seamlessly and protocol handling is in Firmware. -> ?Same as SCSI to ATA translation done in firmware, Ventura controller -> ?is doing SCSI to NVME translation and for end user protocol handling -> ?is abstracted. +> Ventura generation of controllers are adding connectivity of NVME +> drives seamlessly and protocol handling is in Firmware. +> Same as SCSI to ATA translation done in firmware, Ventura controller +> is doing SCSI to NVME translation and for end user protocol handling +> is abstracted. > -> ?This product handles new Transport protocol (NVME) same as ATA and -> ?transport is abstracted for end user. +> This product handles new Transport protocol (NVME) same as ATA and +> transport is abstracted for end user. > > NVME pass-through related driver code, it is just a big tunnel for > user space application. It is just a basic framework like SATA PASS- @@ -72,10 +72,10 @@ SCSI devices regardless of HBA, so we've largely smoothed over any problems if you transfer from mp3sas to another SAS/SATA controller. I believe your current proposal is to have NVMe devices appear as SCSI, -which isn't how the native NVMe driver handles them at all. ?This is +which isn't how the native NVMe driver handles them at all. This is going to have to be special cased in any tool designed to handle nvme devices and it's going to cause big problems if someone changes -controller (or moves the device). ?What's the proposal for making this +controller (or moves the device). What's the proposal for making this as painless as possible? James diff --git a/a/content_digest b/N1/content_digest index 15d3dde..f87797e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,28 +3,39 @@ "ref\020170805135353.GA7526@infradead.org\0" "ref\01501944129.3649.9.camel@HansenPartnership.com\0" "ref\00ada8680ebfeb026662d858ec2b38ef4@mail.gmail.com\0" - "From\0James.Bottomley@hansenpartnership.com (James Bottomley)\0" - "Subject\0[PATCH v2 00/13] mpt3sas driver NVMe support:\0" + "From\0James Bottomley <James.Bottomley@hansenpartnership.com>\0" + "Subject\0Re: [PATCH v2 00/13] mpt3sas driver NVMe support:\0" "Date\0Mon, 07 Aug 2017 07:18:12 -0700\0" + "To\0Kashyap Desai <kashyap.desai@broadcom.com>" + Christoph Hellwig <hch@infradead.org> + " Hannes Reinecke <hare@suse.de>\0" + "Cc\0Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>" + martin.petersen@oracle.com + linux-scsi@vger.kernel.org + Sathya Prakash Veerichetty <sathya.prakash@broadcom.com> + linux-kernel@vger.kernel.org + Chaitra Basappa <chaitra.basappa@broadcom.com> + Sreekanth Reddy <sreekanth.reddy@broadcom.com> + " linux-nvme@lists.infradead.org\0" "\00:1\0" "b\0" - "On Mon, 2017-08-07@19:26 +0530, Kashyap Desai wrote:\n" + "On Mon, 2017-08-07 at 19:26 +0530, Kashyap Desai wrote:\n" "> > \n" "> > -----Original Message-----\n" - "> > From: James Bottomley [mailto:James.Bottomley at HansenPartnership.com\n" + "> > From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com\n" "> > ]\n" "> > Sent: Saturday, August 05, 2017 8:12 PM\n" "> > To: Christoph Hellwig; Hannes Reinecke\n" - "> > Cc: Suganath Prabu S; martin.petersen at oracle.com; linux-\n" - "> > scsi at vger.kernel.org; Sathya.Prakash at broadcom.com;\n" - "> > kashyap.desai at broadcom.com; linux-kernel at vger.kernel.org;\n" - "> > chaitra.basappa at broadcom.com; sreekanth.reddy at broadcom.com; linux-\n" - "> > nvme at lists.infradead.org\n" + "> > Cc: Suganath Prabu S; martin.petersen@oracle.com; linux-\n" + "> > scsi@vger.kernel.org; Sathya.Prakash@broadcom.com;\n" + "> > kashyap.desai@broadcom.com; linux-kernel@vger.kernel.org;\n" + "> > chaitra.basappa@broadcom.com; sreekanth.reddy@broadcom.com; linux-\n" + "> > nvme@lists.infradead.org\n" "> > Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support:\n" "> > \n" - "> > On Sat, 2017-08-05@06:53 -0700, Christoph Hellwig wrote:\n" + "> > On Sat, 2017-08-05 at 06:53 -0700, Christoph Hellwig wrote:\n" "> > > \n" - "> > > On Wed, Aug 02, 2017@10:14:40AM +0200, Hannes Reinecke wrote:\n" + "> > > On Wed, Aug 02, 2017 at 10:14:40AM +0200, Hannes Reinecke wrote:\n" "> > > > \n" "> > > > \n" "> > > > I'm not happy with this approach.\n" @@ -41,7 +52,7 @@ "> > > > other\n" "> > > > NVMe HBA.\n" "> > > \n" - "> > > That doesn't make any sense.??The devices behind the mpt adapter\n" + "> > > That doesn't make any sense.\302\240\302\240The devices behind the mpt adapter\n" "> > > don't\n" "> > > look like NVMe devices at all for the hosts - there are no NVMe\n" "> > > commands or queues involved at all, they hide behind the same\n" @@ -60,14 +71,14 @@ "> > sysfs\n" "> > files as everything else for SAS devices.\n" "> \n" - "> ?Ventura generation of controllers are adding connectivity of NVME\n" - "> ?drives seamlessly and protocol handling is in Firmware.\n" - "> ?Same as SCSI to ATA translation done in firmware, Ventura controller\n" - "> ?is doing SCSI to NVME translation and for end user protocol handling\n" - "> ?is abstracted.\n" + "> \302\240Ventura generation of controllers are adding connectivity of NVME\n" + "> \302\240drives seamlessly and protocol handling is in Firmware.\n" + "> \302\240Same as SCSI to ATA translation done in firmware, Ventura controller\n" + "> \302\240is doing SCSI to NVME translation and for end user protocol handling\n" + "> \302\240is abstracted.\n" "> \n" - "> ?This product handles new Transport protocol (NVME) same as ATA and\n" - "> ?transport is abstracted for end user.\n" + "> \302\240This product handles new Transport protocol (NVME) same as ATA and\n" + "> \302\240transport is abstracted for end user.\n" "> \n" "> NVME pass-through related driver code, it is just a big tunnel for\n" "> user space application. It is just a basic framework like SATA PASS-\n" @@ -82,12 +93,12 @@ "problems if you transfer from mp3sas to another SAS/SATA controller.\n" "\n" "I believe your current proposal is to have NVMe devices appear as SCSI,\n" - "which isn't how the native NVMe driver handles them at all. ?This is\n" + "which isn't how the native NVMe driver handles them at all. \302\240This is\n" "going to have to be special cased in any tool designed to handle nvme\n" "devices and it's going to cause big problems if someone changes\n" - "controller (or moves the device). ?What's the proposal for making this\n" + "controller (or moves the device). \302\240What's the proposal for making this\n" "as painless as possible?\n" "\n" James -f0c1f1e6cf8f2adca47ed49af9b07408ea5581bc9b1985dcd3f16db13984233c +3c2ab160e96941adc244545659121739723b6b165f9ad8d8367a304554850b8b
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.