From: Anand Subramanian <anand.s at samsung.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Testing out the compress/reduce flow
Date: Tue, 13 Nov 2018 00:18:33 +0000 [thread overview]
Message-ID: <2615c5ad39fb42b5be559df6edc743db@samsung.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AB8BF677E@FMSMSX126.amr.corp.intel.com
[-- 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=
next reply other threads:[~2018-11-13 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 0:18 Anand Subramanian [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 0:21 [SPDK] Testing out the compress/reduce flow Luse, Paul E
2018-11-13 0:16 Luse, Paul E
2018-11-13 0:11 Anand Subramanian
2018-11-12 23:40 Harris, James R
2018-11-12 23:24 Luse, Paul E
2018-11-12 23:07 Luse, Paul E
2018-11-12 21:41 Anand Subramanian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2615c5ad39fb42b5be559df6edc743db@samsung.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox