diff for duplicates of <1502120725.2841.28.camel@HansenPartnership.com> diff --git a/a/1.txt b/N1/1.txt index 1a0965d..82025d7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,35 +1,35 @@ -On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote: +On Mon, 2017-08-07 at 20:01 +0530, Kashyap Desai wrote: > > > > -----Original Message----- -> > From: James Bottomley [mailto:James.Bottomley at HansenPartnership.com +> > From: James Bottomley [mailto:James.Bottomley@HansenPartnership.com > > ] > > Sent: Monday, August 07, 2017 7:48 PM > > To: Kashyap Desai; Christoph Hellwig; Hannes Reinecke -> > Cc: Suganath Prabu Subramani; martin.petersen at oracle.com; linux- -> > scsi at vger.kernel.org; Sathya Prakash Veerichetty; linux- -> > kernel at vger.kernel.org; Chaitra Basappa; Sreekanth Reddy; linux- -> > nvme at lists.infradead.org +> > Cc: Suganath Prabu Subramani; martin.petersen@oracle.com; linux- +> > scsi@vger.kernel.org; Sathya Prakash Veerichetty; linux- +> > kernel@vger.kernel.org; Chaitra Basappa; Sreekanth Reddy; linux- +> > nvme@lists.infradead.org > > Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support: > > -> > 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 +> > > > 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; +> > > > 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 at lists.infradead.org +> > > > 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 at 10:14:40AM +0200, Hannes Reinecke @@ -52,7 +52,7 @@ On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote: > > > > > > like > > > > > > any other NVMe HBA. > > > > > -> > > > > That doesn't make any sense.??The devices behind the mpt +> > > > > 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 @@ -72,18 +72,18 @@ On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote: > > > > SAS > > > > devices. > > > -> > > ?Ventura generation of controllers are adding connectivity of +> > > 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 +> > > 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 +> > > is doing SCSI to NVME translation and for end user protocol > > > handling -> > > ?is abstracted. +> > > is abstracted. > > > -> > > ?This product handles new Transport protocol (NVME) same as ATA +> > > This product handles new Transport protocol (NVME) same as ATA > > > and -> > > ?transport is abstracted for end user. +> > > transport is abstracted for end user. > > > > > > NVME pass-through related driver code, it is just a big tunnel > > > for @@ -115,21 +115,21 @@ having us have to support it. > > 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 +> > 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 as painless as +> > device). What's the proposal for making this as painless as > > possible? > > We have to attempt this use case and see how it behaves. I have not > tried this, so not sure if things are really bad or just some tuning > may be helpful. I will revert back to you on this. > -> I understood request as -??We need some udev rules to be working well +> I understood request as - We need some udev rules to be working well > for *same* NVME drives if it is behind <mpt3sas> or native <nvme>. > Example - If user has OS installed on NVME drive which is behind > <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked diff --git a/a/content_digest b/N1/content_digest index 3a6654b..581d626 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,43 +5,54 @@ "ref\00ada8680ebfeb026662d858ec2b38ef4@mail.gmail.com\0" "ref\01502115492.2841.20.camel@HansenPartnership.com\0" "ref\0da1e0ded0c7d4bab1cfa0850488c8fb7@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 08:45:25 -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@20:01 +0530, Kashyap Desai wrote:\n" + "On Mon, 2017-08-07 at 20:01 +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: Monday, August 07, 2017 7:48 PM\n" "> > To: Kashyap Desai; Christoph Hellwig; Hannes Reinecke\n" - "> > Cc: Suganath Prabu Subramani; martin.petersen at oracle.com; linux-\n" - "> > scsi at vger.kernel.org; Sathya Prakash Veerichetty; linux-\n" - "> > kernel at vger.kernel.org; Chaitra Basappa; Sreekanth Reddy; linux-\n" - "> > nvme at lists.infradead.org\n" + "> > Cc: Suganath Prabu Subramani; martin.petersen@oracle.com; linux-\n" + "> > scsi@vger.kernel.org; Sathya Prakash Veerichetty; linux-\n" + "> > kernel@vger.kernel.org; Chaitra Basappa; Sreekanth Reddy; linux-\n" + "> > nvme@lists.infradead.org\n" "> > Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support:\n" "> > \n" - "> > 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" "> > > > \n" "> > > > \n" "> > > > -----Original Message-----\n" - "> > > > From: James Bottomley [mailto:James.Bottomley at HansenPartnership\n" + "> > > > From: James Bottomley [mailto:James.Bottomley@HansenPartnership\n" "> > > > .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;\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;\n" "> > > > linux-\n" - "> > > > nvme at lists.infradead.org\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" "> > > > > \n" "> > > > > On Wed, Aug 02, 2017 at 10:14:40AM +0200, Hannes Reinecke\n" @@ -64,7 +75,7 @@ "> > > > > > like\n" "> > > > > > any other NVMe HBA.\n" "> > > > > \n" - "> > > > > That doesn't make any sense.??The devices behind the mpt\n" + "> > > > > That doesn't make any sense.\302\240\302\240The devices behind the mpt\n" "> > > > > adapter\n" "> > > > > don't look like NVMe devices at all for the hosts - there are\n" "> > > > > no\n" @@ -84,18 +95,18 @@ "> > > > SAS\n" "> > > > devices.\n" "> > > \n" - "> > > ?Ventura generation of controllers are adding connectivity of\n" + "> > > \302\240Ventura generation of controllers are adding connectivity of\n" "> > > NVME\n" - "> > > ?drives seamlessly and protocol handling is in Firmware.\n" - "> > > ?Same as SCSI to ATA translation done in firmware, Ventura\n" + "> > > \302\240drives seamlessly and protocol handling is in Firmware.\n" + "> > > \302\240Same as SCSI to ATA translation done in firmware, Ventura\n" "> > > controller\n" - "> > > ?is doing SCSI to NVME translation and for end user protocol\n" + "> > > \302\240is doing SCSI to NVME translation and for end user protocol\n" "> > > handling\n" - "> > > ?is abstracted.\n" + "> > > \302\240is abstracted.\n" "> > > \n" - "> > > ?This product handles new Transport protocol (NVME) same as ATA\n" + "> > > \302\240This product handles new Transport protocol (NVME) same as ATA\n" "> > > and\n" - "> > > ?transport is abstracted for end user.\n" + "> > > \302\240transport is abstracted for end user.\n" "> > > \n" "> > > NVME pass-through related driver code, it is just a big tunnel\n" "> > > for\n" @@ -127,21 +138,21 @@ "> > I believe your current proposal is to have NVMe devices appear as\n" "> > SCSI,\n" "> > which\n" - "> > isn't how the native NVMe driver handles them at all.??This is\n" + "> > isn't how the native NVMe driver handles them at all.\302\240\302\240This is\n" "> > going to\n" "> > have to\n" "> > be special cased in any tool designed to handle nvme devices and\n" "> > it's\n" "> > going to\n" "> > cause big problems if someone changes controller (or moves the\n" - "> > device).??What's the proposal for making this as painless as\n" + "> > device).\302\240\302\240What's the proposal for making this as painless as\n" "> > possible?\n" "> \n" "> We have to attempt this use case and see how it behaves. I have not\n" "> tried this, so not sure if things are really bad or just some tuning\n" "> may be helpful. I will revert back to you on this.\n" "> \n" - "> I understood request as -??We need some udev rules to be working well\n" + "> I understood request as -\302\240\302\240We need some udev rules to be working well\n" "> for *same* NVME drives if it is behind <mpt3sas> or native <nvme>.\n" "> Example - If user has OS installed on NVME drive which is behind\n" "> <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked\n" @@ -153,4 +164,4 @@ "\n" James -d073b085543324ea851f502172376c714da7c38faebc4b2317e0b79861edce05 +975feceeb202eac5be8091035ae55f160cc1f7daaca31ee16b4ad9dc1e060cc9
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.