diff for duplicates of <1489174661.2548.5.camel@sandisk.com> diff --git a/a/1.txt b/N1/1.txt index 6c17331..1acbe0b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,46 +1,33 @@ On Tue, 2017-01-10 at 22:40 +0000, Chaitanya Kulkarni wrote: > Participants:- > ------------------ -> I'd like to invite developers from different subsystems to discuss an app= -roach towards=A0 -> a unified testing methodology for storage stack and device drivers belong= -s to=A0 +> I'd like to invite developers from different subsystems to discuss an approach towards +> a unified testing methodology for storage stack and device drivers belongs to > different subsystems. ->=20 +> > Topics for Discussion:- > ------------------------------ -> As a part of discussion following are some of the key points which we can= - focus on:- -> 1. What are the common components of the kernel used by the various subsy= -stems? -> 2. What are the potential target drivers which can benefit from this appr= -oach?=A0 -> =A0 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.) -> 3. What are the desired features that can be implemented in this Framewor= -k? -> =A0 (code coverage, unit tests, stress testings, regression, generating C= -occinelle reports etc.)=A0 +> As a part of discussion following are some of the key points which we can focus on:- +> 1. What are the common components of the kernel used by the various subsystems? +> 2. What are the potential target drivers which can benefit from this approach? +> (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.) +> 3. What are the desired features that can be implemented in this Framework? +> (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.) > 4. Desirable Report generation mechanism? > 5. Basic performance validation? -> 6. Whether QEMU can be used to emulate some of the H/W functionality to c= -reate a test=A0 -> =A0 platform? (Optional subsystem specific) +> 6. Whether QEMU can be used to emulate some of the H/W functionality to create a test +> platform? (Optional subsystem specific) -Regarding existing test software: the SRP test software is a thorough test = -of -the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator a= -nd +Regarding existing test software: the SRP test software is a thorough test of +the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator and target drivers and also of the asynchronous I/O subsystem. This test suite -includes experimental support for the NVMeOF drivers. This test suite suppo= -rts -the rdma_rxe driver which means that an Ethernet adapter is sufficient to r= -un +includes experimental support for the NVMeOF drivers. This test suite supports +the rdma_rxe driver which means that an Ethernet adapter is sufficient to run these tests. -Note: the focus of this test suite is the regular I/O path and device remov= -al. +Note: the focus of this test suite is the regular I/O path and device removal. This test suite neither replaces the libiscsi tests nor xfstests. See also https://github.com/bvanassche/srp-test. -Bart.= +Bart. diff --git a/a/content_digest b/N1/content_digest index 6f69340..ba64006 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,48 +15,35 @@ "On Tue, 2017-01-10 at 22:40 +0000, Chaitanya Kulkarni wrote:\n" "> Participants:-\n" "> ------------------\n" - "> I'd like to invite developers from different subsystems to discuss an app=\n" - "roach towards=A0\n" - "> a unified testing methodology for storage stack and device drivers belong=\n" - "s to=A0\n" + "> I'd like to invite developers from different subsystems to discuss an approach towards\302\240\n" + "> a unified testing methodology for storage stack and device drivers belongs to\302\240\n" "> different subsystems.\n" - ">=20\n" + "> \n" "> Topics for Discussion:-\n" "> ------------------------------\n" - "> As a part of discussion following are some of the key points which we can=\n" - " focus on:-\n" - "> 1. What are the common components of the kernel used by the various subsy=\n" - "stems?\n" - "> 2. What are the potential target drivers which can benefit from this appr=\n" - "oach?=A0\n" - "> =A0 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\n" - "> 3. What are the desired features that can be implemented in this Framewor=\n" - "k?\n" - "> =A0 (code coverage, unit tests, stress testings, regression, generating C=\n" - "occinelle reports etc.)=A0\n" + "> As a part of discussion following are some of the key points which we can focus on:-\n" + "> 1. What are the common components of the kernel used by the various subsystems?\n" + "> 2. What are the potential target drivers which can benefit from this approach?\302\240\n" + "> \302\240 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\n" + "> 3. What are the desired features that can be implemented in this Framework?\n" + "> \302\240 (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.)\302\240\n" "> 4. Desirable Report generation mechanism?\n" "> 5. Basic performance validation?\n" - "> 6. Whether QEMU can be used to emulate some of the H/W functionality to c=\n" - "reate a test=A0\n" - "> =A0 platform? (Optional subsystem specific)\n" + "> 6. Whether QEMU can be used to emulate some of the H/W functionality to create a test\302\240\n" + "> \302\240 platform? (Optional subsystem specific)\n" "\n" - "Regarding existing test software: the SRP test software is a thorough test =\n" - "of\n" - "the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator a=\n" - "nd\n" + "Regarding existing test software: the SRP test software is a thorough test of\n" + "the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator and\n" "target drivers and also of the asynchronous I/O subsystem. This test suite\n" - "includes experimental support for the NVMeOF drivers. This test suite suppo=\n" - "rts\n" - "the rdma_rxe driver which means that an Ethernet adapter is sufficient to r=\n" - "un\n" + "includes experimental support for the NVMeOF drivers. This test suite supports\n" + "the rdma_rxe driver which means that an Ethernet adapter is sufficient to run\n" "these tests.\n" "\n" - "Note: the focus of this test suite is the regular I/O path and device remov=\n" - "al.\n" + "Note: the focus of this test suite is the regular I/O path and device removal.\n" "This test suite neither replaces the libiscsi tests nor xfstests.\n" "\n" "See also https://github.com/bvanassche/srp-test.\n" "\n" - Bart.= + Bart. -da5fafc6fdf83d576881d6afe0b78bee52b4d87d0af1ee3dd9f4fe909c8a9ccb +cabdbd345556a419d0ce96a2621b8f0d5eaeb8bd2ae72df0b02f27e3ec962c0f
diff --git a/a/1.txt b/N2/1.txt index 6c17331..debdc57 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,46 +1,33 @@ -On Tue, 2017-01-10 at 22:40 +0000, Chaitanya Kulkarni wrote: +On Tue, 2017-01-10@22:40 +0000, Chaitanya Kulkarni wrote: > Participants:- > ------------------ -> I'd like to invite developers from different subsystems to discuss an app= -roach towards=A0 -> a unified testing methodology for storage stack and device drivers belong= -s to=A0 +> I'd like to invite developers from different subsystems to discuss an approach towards? +> a unified testing methodology for storage stack and device drivers belongs to? > different subsystems. ->=20 +> > Topics for Discussion:- > ------------------------------ -> As a part of discussion following are some of the key points which we can= - focus on:- -> 1. What are the common components of the kernel used by the various subsy= -stems? -> 2. What are the potential target drivers which can benefit from this appr= -oach?=A0 -> =A0 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.) -> 3. What are the desired features that can be implemented in this Framewor= -k? -> =A0 (code coverage, unit tests, stress testings, regression, generating C= -occinelle reports etc.)=A0 +> As a part of discussion following are some of the key points which we can focus on:- +> 1. What are the common components of the kernel used by the various subsystems? +> 2. What are the potential target drivers which can benefit from this approach?? +> ? (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.) +> 3. What are the desired features that can be implemented in this Framework? +> ? (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.)? > 4. Desirable Report generation mechanism? > 5. Basic performance validation? -> 6. Whether QEMU can be used to emulate some of the H/W functionality to c= -reate a test=A0 -> =A0 platform? (Optional subsystem specific) +> 6. Whether QEMU can be used to emulate some of the H/W functionality to create a test? +> ? platform? (Optional subsystem specific) -Regarding existing test software: the SRP test software is a thorough test = -of -the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator a= -nd +Regarding existing test software: the SRP test software is a thorough test of +the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator and target drivers and also of the asynchronous I/O subsystem. This test suite -includes experimental support for the NVMeOF drivers. This test suite suppo= -rts -the rdma_rxe driver which means that an Ethernet adapter is sufficient to r= -un +includes experimental support for the NVMeOF drivers. This test suite supports +the rdma_rxe driver which means that an Ethernet adapter is sufficient to run these tests. -Note: the focus of this test suite is the regular I/O path and device remov= -al. +Note: the focus of this test suite is the regular I/O path and device removal. This test suite neither replaces the libiscsi tests nor xfstests. See also https://github.com/bvanassche/srp-test. -Bart.= +Bart. diff --git a/a/content_digest b/N2/content_digest index 6f69340..7ed2ac6 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,62 +1,42 @@ "ref\0CO2PR04MB218427BF42159B20FB26F74186670@CO2PR04MB2184.namprd04.prod.outlook.com\0" "ref\0CO2PR04MB2184DB653C04FB620B41435486670@CO2PR04MB2184.namprd04.prod.outlook.com\0" - "From\0Bart Van Assche <Bart.VanAssche@sandisk.com>\0" - "Subject\0Re: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\0" + "From\0Bart.VanAssche@sandisk.com (Bart Van Assche)\0" + "Subject\0[LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\0" "Date\0Fri, 10 Mar 2017 19:37:58 +0000\0" - "To\0Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>" - " lsf-pc@lists.linux-foundation.org <lsf-pc@lists.linux-foundation.org>\0" - "Cc\0linux-scsi@vger.kernel.org <linux-scsi@vger.kernel.org>" - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org> - linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> - " linux-ide@vger.kernel.org <linux-ide@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Tue, 2017-01-10 at 22:40 +0000, Chaitanya Kulkarni wrote:\n" + "On Tue, 2017-01-10@22:40 +0000, Chaitanya Kulkarni wrote:\n" "> Participants:-\n" "> ------------------\n" - "> I'd like to invite developers from different subsystems to discuss an app=\n" - "roach towards=A0\n" - "> a unified testing methodology for storage stack and device drivers belong=\n" - "s to=A0\n" + "> I'd like to invite developers from different subsystems to discuss an approach towards?\n" + "> a unified testing methodology for storage stack and device drivers belongs to?\n" "> different subsystems.\n" - ">=20\n" + "> \n" "> Topics for Discussion:-\n" "> ------------------------------\n" - "> As a part of discussion following are some of the key points which we can=\n" - " focus on:-\n" - "> 1. What are the common components of the kernel used by the various subsy=\n" - "stems?\n" - "> 2. What are the potential target drivers which can benefit from this appr=\n" - "oach?=A0\n" - "> =A0 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\n" - "> 3. What are the desired features that can be implemented in this Framewor=\n" - "k?\n" - "> =A0 (code coverage, unit tests, stress testings, regression, generating C=\n" - "occinelle reports etc.)=A0\n" + "> As a part of discussion following are some of the key points which we can focus on:-\n" + "> 1. What are the common components of the kernel used by the various subsystems?\n" + "> 2. What are the potential target drivers which can benefit from this approach??\n" + "> ? (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\n" + "> 3. What are the desired features that can be implemented in this Framework?\n" + "> ? (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.)?\n" "> 4. Desirable Report generation mechanism?\n" "> 5. Basic performance validation?\n" - "> 6. Whether QEMU can be used to emulate some of the H/W functionality to c=\n" - "reate a test=A0\n" - "> =A0 platform? (Optional subsystem specific)\n" + "> 6. Whether QEMU can be used to emulate some of the H/W functionality to create a test?\n" + "> ? platform? (Optional subsystem specific)\n" "\n" - "Regarding existing test software: the SRP test software is a thorough test =\n" - "of\n" - "the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator a=\n" - "nd\n" + "Regarding existing test software: the SRP test software is a thorough test of\n" + "the Linux block layer, SCSI core, dm-mpath driver, dm core, SRP initiator and\n" "target drivers and also of the asynchronous I/O subsystem. This test suite\n" - "includes experimental support for the NVMeOF drivers. This test suite suppo=\n" - "rts\n" - "the rdma_rxe driver which means that an Ethernet adapter is sufficient to r=\n" - "un\n" + "includes experimental support for the NVMeOF drivers. This test suite supports\n" + "the rdma_rxe driver which means that an Ethernet adapter is sufficient to run\n" "these tests.\n" "\n" - "Note: the focus of this test suite is the regular I/O path and device remov=\n" - "al.\n" + "Note: the focus of this test suite is the regular I/O path and device removal.\n" "This test suite neither replaces the libiscsi tests nor xfstests.\n" "\n" "See also https://github.com/bvanassche/srp-test.\n" "\n" - Bart.= + Bart. -da5fafc6fdf83d576881d6afe0b78bee52b4d87d0af1ee3dd9f4fe909c8a9ccb +bf80bac6e15f15e3b29aa250bd1ba07ec6c359300cb7385d241b296e8c931b57
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.