From: Luse, Paul E <paul.e.luse at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: SPDK RAID5 support
Date: Fri, 04 Oct 2019 15:31:43 +0000 [thread overview]
Message-ID: <D3D23831-BCDC-4548-B756-AAD1EDE712C7@intel.com> (raw)
In-Reply-To: d72c2d61-32b4-95a9-99c6-6d58c9c80a69@intel.com
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Agreed. And to save on emails, Artur wrt your response to my email - awesome! And wrt DDF yeah I meant "strict adherence to" - totally agree there's a lot to borrow there if nothing else than to make sure we're covering all of our bases. Looking forward to seeing this get started and I'm definitely going to grab an item or two of the backlog (
Thx
Paul
On 10/4/19, 6:39 AM, "Artur Paszkiewicz" <artur.paszkiewicz(a)intel.com> wrote:
On 10/4/19 12:49 AM, 松本周平 / MATSUMOTO，SHUUHEI wrote:
> Recently SPDK are starting to support DIF feature.
> Can we have any possibility to include the extended LBA (block size = 512 + 8, 4096 + 128, or etc) into SPDK RAID?
Do you mean DIF passthrough? I think this should be included.
Thanks,
Artur
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org
next reply other threads:[~2019-10-04 15:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 15:31 Luse, Paul E [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-21 15:22 [SPDK] Re: SPDK RAID5 support Artur Paszkiewicz
2019-10-16 12:19 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 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=D3D23831-BCDC-4548-B756-AAD1EDE712C7@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