[SPDK] Testing out the compress/reduce flow

[SPDK] Testing out the compress/reduce flow

[Anand Subramanian]

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

Hi Jim, Paul,

Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?

Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?

Thanks,
Anand

Re: [SPDK] Testing out the compress/reduce flow

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]

Hi Anand,

Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  

Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!

Thanks
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 2:42 PM
To: spdk(a)lists.01.org
Subject: [SPDK] Testing out the compress/reduce flow

Hi Jim, Paul,

Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?

Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?

Thanks,
Anand
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] Testing out the compress/reduce flow

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 2524 bytes --]

Actually in prep for UT work if you want to start looking through some other module's unit tests to get a feel for how the test framework is all put together looking at the simple passthru module is probably a good place to start....

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, November 12, 2018 4:08 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Anand,

Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  

Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!

Thanks
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 2:42 PM
To: spdk(a)lists.01.org
Subject: [SPDK] Testing out the compress/reduce flow

Hi Jim, Paul,

Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?

Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?

Thanks,
Anand
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] Testing out the compress/reduce flow

[Harris, James R]

[-- Attachment #1: Type: text/plain, Size: 2851 bytes --]

Hi Anand,

I think the main thing right now is just reviewing patches as they are posted.  I have a series of patches I've been working on locally that I've been trying to get out for review a few patches at a time.  But after Paul and I discussed some of the interfaces last week, we're going to change how the pmem file is opened.  libreduce is going to do that now rather than the user of the library.  I'm reworking those interfaces now and will have 5 hours on planes tomorrow to wrap up those patches and get them out to GerritHub for review.

-Jim


On 11/12/18, 4:07 PM, "SPDK on behalf of Luse, Paul E" <spdk-bounces(a)lists.01.org on behalf of paul.e.luse(a)intel.com> wrote:

    Hi Anand,
    
    Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  
    
    Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!
    
    Thanks
    Paul
    
    -----Original Message-----
    From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
    Sent: Monday, November 12, 2018 2:42 PM
    To: spdk(a)lists.01.org
    Subject: [SPDK] Testing out the compress/reduce flow
    
    Hi Jim, Paul,
    
    Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?
    
    Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?
    
    Thanks,
    Anand
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    

Re: [SPDK] Testing out the compress/reduce flow

[Anand Subramanian]

[-- Attachment #1: Type: text/plain, Size: 4590 bytes --]

Hi Jim, Paul,

Thanks for letting me know. Sounds good. I think initially it would really help to have the pmem interface calls abstracted in the sense that we should ideally be able to run the UTs without a pm device. And for the most part, it would help to be able to test it out with a ramdisk or something (without a real pm device). 

It would really help if you could put out some steps for a UT setup similar to what you folks use, at least for starters before we try other configurations.

Look fwd to the reviews.

Cheers,
Anand

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R
Sent: Monday, November 12, 2018 3:41 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Anand,

I think the main thing right now is just reviewing patches as they are posted.  I have a series of patches I've been working on locally that I've been trying to get out for review a few patches at a time.  But after Paul and I discussed some of the interfaces last week, we're going to change how the pmem file is opened.  libreduce is going to do that now rather than the user of the library.  I'm reworking those interfaces now and will have 5 hours on planes tomorrow to wrap up those patches and get them out to GerritHub for review.

-Jim


On 11/12/18, 4:07 PM, "SPDK on behalf of Luse, Paul E" <spdk-bounces(a)lists.01.org on behalf of paul.e.luse(a)intel.com> wrote:

    Hi Anand,
    
    Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  
    
    Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!
    
    Thanks
    Paul
    
    -----Original Message-----
    From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
    Sent: Monday, November 12, 2018 2:42 PM
    To: spdk(a)lists.01.org
    Subject: [SPDK] Testing out the compress/reduce flow
    
    Hi Jim, Paul,
    
    Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?
    
    Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?
    
    Thanks,
    Anand
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=
    

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=

Re: [SPDK] Testing out the compress/reduce flow

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 5650 bytes --]

Yeah, that's why I suggested looking at the passthru vbdev module unit tests.  Our unit tests are a a mix of home-grown stuff and cunit.  There will be separate UT modules for the reducelib (Jim has at least some of that done already) and the vbdev module.  What I've got for you to cut your teeth on is the vbdev UT basics so there won't be any compression or pmem stuff here but it's a great way to learn how out UT framework works.  Once the vbdev interfaces to Jim's library and the DPDK library are in there will, of course, be UT for those functions that mock the interfaces - that's the part that won't be there for a little while.

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 5:11 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Jim, Paul,

Thanks for letting me know. Sounds good. I think initially it would really help to have the pmem interface calls abstracted in the sense that we should ideally be able to run the UTs without a pm device. And for the most part, it would help to be able to test it out with a ramdisk or something (without a real pm device). 

It would really help if you could put out some steps for a UT setup similar to what you folks use, at least for starters before we try other configurations.

Look fwd to the reviews.

Cheers,
Anand

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R
Sent: Monday, November 12, 2018 3:41 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Anand,

I think the main thing right now is just reviewing patches as they are posted.  I have a series of patches I've been working on locally that I've been trying to get out for review a few patches at a time.  But after Paul and I discussed some of the interfaces last week, we're going to change how the pmem file is opened.  libreduce is going to do that now rather than the user of the library.  I'm reworking those interfaces now and will have 5 hours on planes tomorrow to wrap up those patches and get them out to GerritHub for review.

-Jim


On 11/12/18, 4:07 PM, "SPDK on behalf of Luse, Paul E" <spdk-bounces(a)lists.01.org on behalf of paul.e.luse(a)intel.com> wrote:

    Hi Anand,
    
    Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  
    
    Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!
    
    Thanks
    Paul
    
    -----Original Message-----
    From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
    Sent: Monday, November 12, 2018 2:42 PM
    To: spdk(a)lists.01.org
    Subject: [SPDK] Testing out the compress/reduce flow
    
    Hi Jim, Paul,
    
    Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?
    
    Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?
    
    Thanks,
    Anand
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=
    

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwIGaQ&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=d1rIGsz4g34kRr5kmRLZlJH1D9x9Kie2K6dEnORFiOw&s=mGa0QuxmhKd0govK6zdAej4AHhKaw94vg_xiLYQTOYM&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] Testing out the compress/reduce flow

[Anand Subramanian]

[-- Attachment #1: Type: text/plain, Size: 4038 bytes --]

Hi Paul,

Thanks for the tip! I will look at that sor sure. (I am unable to access IRC chat and probably won't be able to do so for the next few weeks, so I might have to send you an individual email while I get the test setup going. If it works, I'll be sure to document that for the community at large).

Thanks
Anand

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, November 12, 2018 3:24 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Actually in prep for UT work if you want to start looking through some other module's unit tests to get a feel for how the test framework is all put together looking at the simple passthru module is probably a good place to start....

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, November 12, 2018 4:08 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Anand,

Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  

Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!

Thanks
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 2:42 PM
To: spdk(a)lists.01.org
Subject: [SPDK] Testing out the compress/reduce flow

Hi Jim, Paul,

Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?

Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?

Thanks,
Anand
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=

Re: [SPDK] Testing out the compress/reduce flow

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 4817 bytes --]

Oh I'm sure there are more folks out there that would love to see the Q&A on the SPDK unit test setup, trust me! Some of it can be pretty tricky so please feel free to use this dist list.  People can always ignore if they aren't interested :) 

If you're really feeling adventurous, take notes along the way and considering doing a blog post on the SPDK site!

-Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 5:19 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Paul,

Thanks for the tip! I will look at that sor sure. (I am unable to access IRC chat and probably won't be able to do so for the next few weeks, so I might have to send you an individual email while I get the test setup going. If it works, I'll be sure to document that for the community at large).

Thanks
Anand

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, November 12, 2018 3:24 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Actually in prep for UT work if you want to start looking through some other module's unit tests to get a feel for how the test framework is all put together looking at the simple passthru module is probably a good place to start....

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, November 12, 2018 4:08 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Testing out the compress/reduce flow

Hi Anand,

Thanks for asking! Yes, there's always ways to help :)  As you know Jim is doing the SPDK reduce library so I'll let him comment on what might make sense there.  I'm doing the vbdev module and I'm probably just a few days away from being able to use some help with unit test. Right now I'm in the middle of getting the path app<-->vbdev<-->dpdk compressdev<-->bdev> coded and there will likely be a little throw away work there because once it interfaces with the reduce lib a lot of things will change however we want to make sure, since both compressdev API and reduclibe API are new, that we can test them individually through the vbdev first.  With Jim's library we'll even be able to test the complete path without doing any real compression, etc.  

Stay tuned and don't ever hesitate to hit us up on the mailing list.  I'll send a note out later this week and let you know the best time to start -  initially it will be a patch based on the vbdev compress patch that start by adding the basic framework for UT and can cover the non-compression centric functions. Won't be long!

Thanks
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Anand Subramanian
Sent: Monday, November 12, 2018 2:42 PM
To: spdk(a)lists.01.org
Subject: [SPDK] Testing out the compress/reduce flow

Hi Jim, Paul,

Is there any way to help test out the basic flows for the md or the data for the compress/reduce work so far?

Is there an easy way to setup a testbed for this without pm (some steps to maybe repro the compress lvol or to setup what you folks have would help)? Maybe that will help w.r.t. some initial testing and/or fixing of some of the initial low-hanging issues?

Thanks,
Anand
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_mailman_listinfo_spdk&d=DwICAg&c=JfeWlBa6VbDyTXraMENjy_b_0yKWuqQ4qY-FPhxK4x8w-TfgRBDyeV4hVQQBEgL2&r=WDvM24o7tXcmRRL6eRTRZUTaIuukZ9NPcFO9eKhUBVs&m=pJ0mt-3AI6NvhveXIADfTMftxrjLIe-qS9X0ufCEO6A&s=nTmSNjZZvV39ItN7oveO-GAGrhy6iymET5-lRfJNY8k&e=
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk