From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] [PATCH 1/2] libibverbs: Allow 3rd party extensions to verb routines
Date: Mon, 06 Jun 2011 11:30:30 -0500 [thread overview]
Message-ID: <4DED00A6.4010201@opengridcomputing.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373012B5B-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 06/03/2011 07:34 PM, Hefty, Sean wrote:
> In order to support OFED or vendor specific calls, define a
> generic extension mechanism. This allows OFED, an RDMA vendor,
> or another registered 3rd party (for example, the librdmacm)
> to define RDMA extensions.
>
Will this mechanism allow an RDMA provider driver to export a new qp-related operation for use internally bit the
supporting provider library? IE Not exposes to the RDMA application, but an internal interface between the library and
driver. I have need for this with the T4 driver.
> Users which make use extensions are aware that they are not
> only using an extended call, but are given information regarding
> how widely the extension by be supported.
Can you expand on the above sentence? I don't get the "how widely supported" angle?
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
next prev parent reply other threads:[~2011-06-06 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 0:34 [RFC] [PATCH 1/2] libibverbs: Allow 3rd party extensions to verb routines Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373012B5B-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-06-04 4:39 ` Weiny, Ira K.
[not found] ` <6E0AE576-9B92-46E4-A5F6-68ECD64C5B67-i2BcT+NCU+M@public.gmane.org>
2011-06-05 13:47 ` Hefty, Sean
2011-06-06 16:30 ` Steve Wise [this message]
[not found] ` <4DED00A6.4010201-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-06-06 18:07 ` Roland Dreier
[not found] ` <BANLkTikvz7grX-7qaovTpgDb+0B1zwQPJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-06 18:28 ` Steve Wise
[not found] ` <4DED105B.1020807@opengridcomputing.com>
[not found] ` <4DED105B.1020807-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2011-06-06 18:28 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373017894-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-06-06 18:35 ` Steve Wise
2011-06-09 16:55 ` Jason Gunthorpe
[not found] ` <20110609165528.GA6257-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-06-09 18:59 ` Hefty, Sean
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=4DED00A6.4010201@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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.