From: sagi grimberg <sagig@mellanox.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>
Cc: Oren Duer <oren@mellanox.com>
Subject: [LSF/MM TOPIC][ATTEND] T10-PI RDMA offload
Date: Thu, 16 Jan 2014 14:26:30 +0200 [thread overview]
Message-ID: <52D7CFF6.4030901@mellanox.com> (raw)
Hey SCSI folks,
I'd like to propose the following topic for upcoming LSF-MM:
T10-PI standard is becoming more and more appealing for storage and
cloud solutions. Since error-detection
coding comes with its cost of CPU computation overhead, state-of-the-art
ASICs offer the ability to offload
T10-PI operations (DIF/DIX), examples are SAS & FC controllers.
Recently, the support for T10-PI offload over
RDMA transactions was introduced in the Mellanox Connect-IB HCA.
The first building block, RDMA verbs API supporting T10-PI offload was
submitted over Linux-rdma (see
http://marc.info/?l=linux-rdma&m=138719320307936&w=2). Moreover, We have
seen first seeds of T10-PI
support in Linux SCSI target entering v3.14 (see
http://lwn.net/Articles/579708/) and RDMA offload
implementation in iSER transport (see
http://www.spinics.net/lists/linux-scsi/msg71128.html). There is
still some ground to fill to get protection information support to a
full solution over all backend devices.
We would like to use LSF-MM platform to to push forward T10-PI support
end-to-end which requires Linux SCSI
Target core level support along with transport level support in iSER and
SRP (and also FCoE in the future) and
over to the Initiator side transports.
Discussion topics:
- Introduce T10-PI offload RDMA verbs and how are used in storage
applications.
- Discuss effects of DIX1.1 (currently a draft) in Target implementation
(core level -> transport level -> HW level).
- Discuss T10-PI Type 4 (16-byte DIF) status and possible implications
on Target & Initiator implementation down to HW level.
- Discuss Current Limitations that T10-PI RDMA offload poses on iSCSI
protocol (ImmediateData, UnsolDataOut) and if/how they can be solved.
- What-ever else comes to mind...
Thanks,
Sagi.
next reply other threads:[~2014-01-16 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:26 sagi grimberg [this message]
2014-01-16 14:33 ` [LSF/MM TOPIC][ATTEND] T10-PI RDMA offload James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 15:12 Sagi Grimberg
2014-01-16 21:22 ` Nicholas A. Bellinger
2014-01-17 0:47 ` Quinn Tran
2014-01-20 12:51 ` Bart Van Assche
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=52D7CFF6.4030901@mellanox.com \
--to=sagig@mellanox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=oren@mellanox.com \
--cc=target-devel@vger.kernel.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 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.