All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: IETF draft: RDMA Protocol Extensions
Date: Mon, 02 Dec 2013 11:23:11 -0600	[thread overview]
Message-ID: <529CC1FF.7010101@opengridcomputing.com> (raw)
In-Reply-To: <f1e78b8b394ddacf82f0358b1400e6d6-zgzEX58YAwA@public.gmane.org>

On 11/29/2013 4:16 AM, Yann Droneaud wrote:
> Hi,
>
> I've just seen the following IETF drafts:
>
> - "RDMA Protocol Extensions", draft-ietf-storm-rdmap-ext-08.txt, by
> Hemal Shah, Felix Marti, Wael Noureddine, Asgeir Eiriksson and Robert 
> Sharp:
>
> http://tools.ietf.org/html/draft-ietf-storm-rdmap-ext-08
>
> "Abstract
>
>    This document specifies extensions to the IETF Remote Direct Memory
>    Access Protocol (RDMAP [RFC5040]). RDMAP provides read and write
>    services directly to applications and enables data to be transferred
>    directly into Upper Layer Protocol (ULP) Buffers without
>    intermediate data copies. The extensions specified in this document
>    provide the following capabilities and/or improvements: Atomic
>    Operations and Immediate Data."
> "
>
> 5. Atomic Operations
> http://tools.ietf.org/html/draft-ietf-storm-rdmap-ext-08#section-5
>
> 6. Immediate Data
> http://tools.ietf.org/html/draft-ietf-storm-rdmap-ext-08#section-6
>
> - "RDMA Protocol Extensions V2", draft-wood-storm-rdmap-ext-v2-00.txt, by
> Donald Wood, Robert Sharp and Kenneth Keels:
>
> http://tools.ietf.org/html/draft-wood-storm-rdmap-ext-v2-00
>
> "
> Abstract
>
>    This document specifies extensions to the IETF Remote Direct Memory
>    Access Protocol and RDMA Protocol Extensions. RDMAP provides read
>    and write services directly to applications and enables data to be
>    transferred directly into Upper Layer Protocol (ULP) Buffers without
>    intermediate data copies. The extensions specified in this document
>    provide the following capabilities and/or improvements to eliminate
>    application visible differences with other RDMA technologies: Send
>    with Immediate Data Operations and a new form of RDMA Read
>    Operation.
> "
>
> 5. Send with Immediate Data Operations:
> http://tools.ietf.org/html/draft-wood-storm-rdmap-ext-v2-00#section-5
>
> 6. RDMA Read V2:
> http://tools.ietf.org/html/draft-wood-storm-rdmap-ext-v2-00#section-6
>
> Is there someone involved in these drafts on the list that could explain
> how it will impact Linux RDMA implementation ?
>

Any iWARP providers that support these will be impacted probably in 
device-specific ways in order to support these new operations.   The 
core iwcm might be impacted, but I can't think of how it would be at 
this point.  I wouldn't think any other core modules will be impacted.

Probably we'll have to come up with some way to allow applications to 
know whether the device supports these features.  Currently most 
applications key on the transport type to decide about whether these 
features are supported or not.  We should allow them to key on the 
feature support instead perhaps.

Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2013-12-02 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 10:16 IETF draft: RDMA Protocol Extensions Yann Droneaud
     [not found] ` <f1e78b8b394ddacf82f0358b1400e6d6-zgzEX58YAwA@public.gmane.org>
2013-12-02 17:23   ` Steve Wise [this message]

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=529CC1FF.7010101@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.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.