diff for duplicates of <20170111091945.GD6286@linux-x5ow.site> diff --git a/a/1.txt b/N1/1.txt index 7817f50..5cd8792 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,7 +6,7 @@ On Tue, Jan 10, 2017 at 10:40:53PM +0000, Chaitanya Kulkarni wrote: > To: lsf-pc@lists.linux-foundation.org > Cc: linux-fsdevel@vger.kernel.org; linux-block@vger.kernel.org; linux-nvme@lists.infradead.org; linux-scsi@vger.kernel.org; linux-ide@vger.kernel.org > Subject: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology. -> � +> > > Hi Folks, > @@ -14,48 +14,48 @@ On Tue, Jan 10, 2017 at 10:40:53PM +0000, Chaitanya Kulkarni wrote: > > Purpose:- > ------------- -> The main objective of this discussion is to address the need for� +> The main objective of this discussion is to address the need for > a Unified Test Automation Framework which can be used by different subsystems > in the kernel in order to improve the overall development and stability > of the storage stack. > -> For Example:-� +> For Example:- > From my previous experience, I've worked on the NVMe driver testing last year and we > have developed simple unit test framework -> �(https://github.com/linux-nvme/nvme-cli/tree/master/tests).� +> (https://github.com/linux-nvme/nvme-cli/tree/master/tests). > In current implementation Upstream NVMe Driver supports following subsystems:- > 1. PCI Host. > 2. RDMA Target. > 3. Fiber Channel Target (in progress). -> Today due to lack of centralized automated test framework NVMe Driver testing is� -> scattered and performed using the combination of various utilities like nvme-cli/tests,� +> Today due to lack of centralized automated test framework NVMe Driver testing is +> scattered and performed using the combination of various utilities like nvme-cli/tests, > nvmet-cli, shell scripts (git://git.infradead.org/nvme-fabrics.git nvmf-selftests) etc. > > In order to improve overall driver stability with various subsystems, it will be beneficial > to have a Unified Test Automation Framework (UTAF) which will centralize overall -> testing.� +> testing. > -> This topic will allow developers from various subsystem engage in the discussion about� +> This topic will allow developers from various subsystem engage in the discussion about > how to collaborate efficiently instead of having discussions on lengthy email threads. > > Participants:- > ------------------ -> 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� +> 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. > > 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 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.) +> 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.)� +> (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 create a test� -> � 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) Well, something I was thinking about but didn't find enough time to actually implement is making a xfstestes like test suite written using sg3_utils for @@ -66,7 +66,7 @@ Byte, -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 -SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg -GF: Felix Imend�rffer, Jane Smithard, Graham Norton -HRB 21284 (AG N�rnberg) +SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg +GF: Felix Imendörffer, Jane Smithard, Graham Norton +HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 diff --git a/a/content_digest b/N1/content_digest index 07fd12a..b213626 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -20,7 +20,7 @@ "> To: lsf-pc@lists.linux-foundation.org\n" "> Cc: linux-fsdevel@vger.kernel.org; linux-block@vger.kernel.org; linux-nvme@lists.infradead.org; linux-scsi@vger.kernel.org; linux-ide@vger.kernel.org\n" "> Subject: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\n" - "> \303\257\302\277\302\275 \n" + "> \302\240 \n" "> \n" "> Hi Folks,\n" "> \n" @@ -28,48 +28,48 @@ "> \n" "> Purpose:-\n" "> -------------\n" - "> The main objective of this discussion is to address the need for\303\257\302\277\302\275\n" + "> The main objective of this discussion is to address the need for\302\240\n" "> a Unified Test Automation Framework which can be used by different subsystems\n" "> in the kernel in order to improve the overall development and stability\n" "> of the storage stack.\n" "> \n" - "> For Example:-\303\257\302\277\302\275\n" + "> For Example:-\302\240\n" "> From my previous experience, I've worked on the NVMe driver testing last year and we\n" "> have developed simple unit test framework\n" - "> \303\257\302\277\302\275(https://github.com/linux-nvme/nvme-cli/tree/master/tests).\303\257\302\277\302\275\n" + "> \302\240(https://github.com/linux-nvme/nvme-cli/tree/master/tests).\302\240\n" "> In current implementation Upstream NVMe Driver supports following subsystems:-\n" "> 1. PCI Host.\n" "> 2. RDMA Target.\n" "> 3. Fiber Channel Target (in progress).\n" - "> Today due to lack of centralized automated test framework NVMe Driver testing is\303\257\302\277\302\275\n" - "> scattered and performed using the combination of various utilities like nvme-cli/tests,\303\257\302\277\302\275\n" + "> Today due to lack of centralized automated test framework NVMe Driver testing is\302\240\n" + "> scattered and performed using the combination of various utilities like nvme-cli/tests,\302\240\n" "> nvmet-cli, shell scripts (git://git.infradead.org/nvme-fabrics.git nvmf-selftests) etc.\n" "> \n" "> In order to improve overall driver stability with various subsystems, it will be beneficial\n" "> to have a Unified Test Automation Framework (UTAF) which will centralize overall\n" - "> testing.\303\257\302\277\302\275\n" + "> testing.\302\240\n" "> \n" - "> This topic will allow developers from various subsystem engage in the discussion about\303\257\302\277\302\275\n" + "> This topic will allow developers from various subsystem engage in the discussion about\302\240\n" "> how to collaborate efficiently instead of having discussions on lengthy email threads.\n" "> \n" "> Participants:-\n" "> ------------------\n" - "> I'd like to invite developers from different subsystems to discuss an approach towards\303\257\302\277\302\275\n" - "> a unified testing methodology for storage stack and device drivers belongs to\303\257\302\277\302\275\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" "> \n" "> Topics for Discussion:-\n" "> ------------------------------\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?\303\257\302\277\302\275\n" - "> \303\257\302\277\302\275 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\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" - "> \303\257\302\277\302\275 (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.)\303\257\302\277\302\275\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 create a test\303\257\302\277\302\275\n" - "> \303\257\302\277\302\275 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" "Well, something I was thinking about but didn't find enough time to actually\n" "implement is making a xfstestes like test suite written using sg3_utils for\n" @@ -80,9 +80,9 @@ "-- \n" "Johannes Thumshirn Storage\n" "jthumshirn@suse.de +49 911 74053 689\n" - "SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N\303\257\302\277\302\275rnberg\n" - "GF: Felix Imend\303\257\302\277\302\275rffer, Jane Smithard, Graham Norton\n" - "HRB 21284 (AG N\303\257\302\277\302\275rnberg)\n" + "SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N\303\274rnberg\n" + "GF: Felix Imend\303\266rffer, Jane Smithard, Graham Norton\n" + "HRB 21284 (AG N\303\274rnberg)\n" Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 -9958f0be8726516f4c7a96da8adbf41b06057c257487bdc384c740a332893330 +3d4e88a434a34574d8f6575679e60da610fa1d19439096b17b0e7a12dc41cd5d
diff --git a/a/1.txt b/N2/1.txt index 7817f50..f8cb29a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,12 +1,12 @@ -On Tue, Jan 10, 2017 at 10:40:53PM +0000, Chaitanya Kulkarni wrote: +On Tue, Jan 10, 2017@10:40:53PM +0000, Chaitanya Kulkarni wrote: > Resending it at as a plain text. > > From: Chaitanya Kulkarni > Sent: Tuesday, January 10, 2017 2:37 PM -> To: lsf-pc@lists.linux-foundation.org -> Cc: linux-fsdevel@vger.kernel.org; linux-block@vger.kernel.org; linux-nvme@lists.infradead.org; linux-scsi@vger.kernel.org; linux-ide@vger.kernel.org +> To: lsf-pc at lists.linux-foundation.org +> Cc: linux-fsdevel at vger.kernel.org; linux-block at vger.kernel.org; linux-nvme at lists.infradead.org; linux-scsi at vger.kernel.org; linux-ide at vger.kernel.org > Subject: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology. -> � +> ? > > Hi Folks, > @@ -14,48 +14,48 @@ On Tue, Jan 10, 2017 at 10:40:53PM +0000, Chaitanya Kulkarni wrote: > > Purpose:- > ------------- -> The main objective of this discussion is to address the need for� +> The main objective of this discussion is to address the need for? > a Unified Test Automation Framework which can be used by different subsystems > in the kernel in order to improve the overall development and stability > of the storage stack. > -> For Example:-� +> For Example:-? > From my previous experience, I've worked on the NVMe driver testing last year and we > have developed simple unit test framework -> �(https://github.com/linux-nvme/nvme-cli/tree/master/tests).� +> ?(https://github.com/linux-nvme/nvme-cli/tree/master/tests).? > In current implementation Upstream NVMe Driver supports following subsystems:- > 1. PCI Host. > 2. RDMA Target. > 3. Fiber Channel Target (in progress). -> Today due to lack of centralized automated test framework NVMe Driver testing is� -> scattered and performed using the combination of various utilities like nvme-cli/tests,� +> Today due to lack of centralized automated test framework NVMe Driver testing is? +> scattered and performed using the combination of various utilities like nvme-cli/tests,? > nvmet-cli, shell scripts (git://git.infradead.org/nvme-fabrics.git nvmf-selftests) etc. > > In order to improve overall driver stability with various subsystems, it will be beneficial > to have a Unified Test Automation Framework (UTAF) which will centralize overall -> testing.� +> testing.? > -> This topic will allow developers from various subsystem engage in the discussion about� +> This topic will allow developers from various subsystem engage in the discussion about? > how to collaborate efficiently instead of having discussions on lengthy email threads. > > Participants:- > ------------------ -> 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� +> 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. > > 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 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.) +> 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.)� +> ? (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 create a test� -> � 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) Well, something I was thinking about but didn't find enough time to actually implement is making a xfstestes like test suite written using sg3_utils for @@ -65,8 +65,8 @@ Byte, Johannes -- Johannes Thumshirn Storage -jthumshirn@suse.de +49 911 74053 689 -SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg -GF: Felix Imend�rffer, Jane Smithard, Graham Norton -HRB 21284 (AG N�rnberg) +jthumshirn at suse.de +49 911 74053 689 +SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg +GF: Felix Imend?rffer, Jane Smithard, Graham Norton +HRB 21284 (AG N?rnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 diff --git a/a/content_digest b/N2/content_digest index 07fd12a..7adf81f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,26 +1,19 @@ "ref\0CO2PR04MB218427BF42159B20FB26F74186670@CO2PR04MB2184.namprd04.prod.outlook.com\0" "ref\0CO2PR04MB2184DB653C04FB620B41435486670@CO2PR04MB2184.namprd04.prod.outlook.com\0" - "From\0Johannes Thumshirn <jthumshirn@suse.de>\0" - "Subject\0Re: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\0" + "From\0jthumshirn@suse.de (Johannes Thumshirn)\0" + "Subject\0[LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\0" "Date\0Wed, 11 Jan 2017 10:19:45 +0100\0" - "To\0Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>\0" - "Cc\0lsf-pc@lists.linux-foundation.org <lsf-pc@lists.linux-foundation.org>" - linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org> - linux-scsi@vger.kernel.org <linux-scsi@vger.kernel.org> - " linux-ide@vger.kernel.org <linux-ide@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Tue, Jan 10, 2017 at 10:40:53PM +0000, Chaitanya Kulkarni wrote:\n" + "On Tue, Jan 10, 2017@10:40:53PM +0000, Chaitanya Kulkarni wrote:\n" "> Resending it at as a plain text.\n" "> \n" "> From: Chaitanya Kulkarni\n" "> Sent: Tuesday, January 10, 2017 2:37 PM\n" - "> To: lsf-pc@lists.linux-foundation.org\n" - "> Cc: linux-fsdevel@vger.kernel.org; linux-block@vger.kernel.org; linux-nvme@lists.infradead.org; linux-scsi@vger.kernel.org; linux-ide@vger.kernel.org\n" + "> To: lsf-pc at lists.linux-foundation.org\n" + "> Cc: linux-fsdevel at vger.kernel.org; linux-block at vger.kernel.org; linux-nvme at lists.infradead.org; linux-scsi at vger.kernel.org; linux-ide at vger.kernel.org\n" "> Subject: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.\n" - "> \303\257\302\277\302\275 \n" + "> ? \n" "> \n" "> Hi Folks,\n" "> \n" @@ -28,48 +21,48 @@ "> \n" "> Purpose:-\n" "> -------------\n" - "> The main objective of this discussion is to address the need for\303\257\302\277\302\275\n" + "> The main objective of this discussion is to address the need for?\n" "> a Unified Test Automation Framework which can be used by different subsystems\n" "> in the kernel in order to improve the overall development and stability\n" "> of the storage stack.\n" "> \n" - "> For Example:-\303\257\302\277\302\275\n" + "> For Example:-?\n" "> From my previous experience, I've worked on the NVMe driver testing last year and we\n" "> have developed simple unit test framework\n" - "> \303\257\302\277\302\275(https://github.com/linux-nvme/nvme-cli/tree/master/tests).\303\257\302\277\302\275\n" + "> ?(https://github.com/linux-nvme/nvme-cli/tree/master/tests).?\n" "> In current implementation Upstream NVMe Driver supports following subsystems:-\n" "> 1. PCI Host.\n" "> 2. RDMA Target.\n" "> 3. Fiber Channel Target (in progress).\n" - "> Today due to lack of centralized automated test framework NVMe Driver testing is\303\257\302\277\302\275\n" - "> scattered and performed using the combination of various utilities like nvme-cli/tests,\303\257\302\277\302\275\n" + "> Today due to lack of centralized automated test framework NVMe Driver testing is?\n" + "> scattered and performed using the combination of various utilities like nvme-cli/tests,?\n" "> nvmet-cli, shell scripts (git://git.infradead.org/nvme-fabrics.git nvmf-selftests) etc.\n" "> \n" "> In order to improve overall driver stability with various subsystems, it will be beneficial\n" "> to have a Unified Test Automation Framework (UTAF) which will centralize overall\n" - "> testing.\303\257\302\277\302\275\n" + "> testing.?\n" "> \n" - "> This topic will allow developers from various subsystem engage in the discussion about\303\257\302\277\302\275\n" + "> This topic will allow developers from various subsystem engage in the discussion about?\n" "> how to collaborate efficiently instead of having discussions on lengthy email threads.\n" "> \n" "> Participants:-\n" "> ------------------\n" - "> I'd like to invite developers from different subsystems to discuss an approach towards\303\257\302\277\302\275\n" - "> a unified testing methodology for storage stack and device drivers belongs to\303\257\302\277\302\275\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" "> \n" "> Topics for Discussion:-\n" "> ------------------------------\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?\303\257\302\277\302\275\n" - "> \303\257\302\277\302\275 (e.g. NVMe, NVMe Over Fabric, Open Channel Solid State Drives etc.)\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" - "> \303\257\302\277\302\275 (code coverage, unit tests, stress testings, regression, generating Coccinelle reports etc.)\303\257\302\277\302\275\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 create a test\303\257\302\277\302\275\n" - "> \303\257\302\277\302\275 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" "Well, something I was thinking about but didn't find enough time to actually\n" "implement is making a xfstestes like test suite written using sg3_utils for\n" @@ -79,10 +72,10 @@ "\tJohannes\n" "-- \n" "Johannes Thumshirn Storage\n" - "jthumshirn@suse.de +49 911 74053 689\n" - "SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N\303\257\302\277\302\275rnberg\n" - "GF: Felix Imend\303\257\302\277\302\275rffer, Jane Smithard, Graham Norton\n" - "HRB 21284 (AG N\303\257\302\277\302\275rnberg)\n" + "jthumshirn at suse.de +49 911 74053 689\n" + "SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg\n" + "GF: Felix Imend?rffer, Jane Smithard, Graham Norton\n" + "HRB 21284 (AG N?rnberg)\n" Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 -9958f0be8726516f4c7a96da8adbf41b06057c257487bdc384c740a332893330 +b651a50018cd9acba7c45a74ebc71e8e7d3142d1b3e74d9492b676b29849a8b8
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.