From: Artur Paszkiewicz <artur.paszkiewicz at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: SPDK RAID5 support
Date: Mon, 21 Oct 2019 17:22:23 +0200 [thread overview]
Message-ID: <40d466bb-06e6-95c7-9e6e-e70d90591e65@intel.com> (raw)
In-Reply-To: D040375D0E8D514EBFFEA29525F27B8C3C6BDF41@SHSMSX104.ccr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On 10/11/19 5:32 PM, Liu, Xiaodong wrote:
> Great work! Artur.
> By the way, do you have some draft or RFC code about your RAID5 support? So we can have a better overall understanding on where the refactoring is towards to.
You can find it here: https://github.com/apaszkie/spdk/tree/raid5_poc/lib/bdev/collections
Please keep in mind that the raid5 was just a piece of a larger POC project, I had to remove all the unrelated parts and cut out a lot of stuff before uploading. I won't try to port this 1:1 but rather use it as a reference for the new implementation.
Regards,
Artur
next reply other threads:[~2019-10-21 15:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 15:22 Artur Paszkiewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-16 12:19 [SPDK] Re: SPDK RAID5 support Sasha Kotchubievsky
2019-10-15 21:21 Sasha Kotchubievsky
2019-10-14 17:43 Harris, James R
2019-10-13 18:18 Luse, Paul E
2019-10-13 17:39 Luse, Paul E
2019-10-13 9:26 Sasha Kotchubievsky
2019-10-13 8:56 Sasha Kotchubievsky
2019-10-11 15:37 Luse, Paul E
2019-10-11 15:32 Liu, Xiaodong
2019-10-11 13:08 Luse, Paul E
2019-10-11 13:07 Artur Paszkiewicz
2019-10-08 20:21 Luse, Paul E
2019-10-08 18:25 David Butterfield
2019-10-04 15:31 Luse, Paul E
2019-10-04 13:38 Artur Paszkiewicz
2019-10-04 13:24 Artur Paszkiewicz
2019-10-03 22:49
2019-10-03 20:44 Marushak, Nathan
2019-10-03 19:20 Luse, Paul E
2019-10-03 16:11 Luse, Paul E
2019-10-03 15:55 David Butterfield
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=40d466bb-06e6-95c7-9e6e-e70d90591e65@intel.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