From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next V2 3/6] IB/mlx5: Add support for QP with a given source QPN
Date: Thu, 8 Jun 2017 10:30:20 -0600 [thread overview]
Message-ID: <20170608163020.GA16857@obsidianresearch.com> (raw)
In-Reply-To: <20170608131511.21040-4-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Thu, Jun 08, 2017 at 04:15:08PM +0300, Leon Romanovsky wrote:
> From: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>
> Allow user space applications to accelerate send and receive
> traffic which is typically handled by IPoIB ULP by creating
> a UD QP with a given source QPN of the IPoIB UD QP.
>
> UD QP with a given source QPN should basically be similar to
> RAW QP from point of view of its created resources.
>
> However,
> - Its TIS should point to the source QPN.
> - Modify can be done only on its state as the transport attributes
> are managed by its source QP.
I thought the discussion conclusion was to get rid of this confusing
linkage from the API?
Jason
--
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:[~2017-06-08 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 13:15 [PATCH rdma-next V2 0/6] Enable flow steering on IPoIB UD QP Leon Romanovsky
[not found] ` <20170608131511.21040-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-08 13:15 ` [PATCH rdma-next V2 1/6] IB/core: Enable QP creation with a given source QP number Leon Romanovsky
2017-06-08 13:15 ` [PATCH rdma-next V2 2/6] IB/uverbs: " Leon Romanovsky
2017-06-08 13:15 ` [PATCH rdma-next V2 3/6] IB/mlx5: Add support for QP with a given source QPN Leon Romanovsky
[not found] ` <20170608131511.21040-4-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-08 16:30 ` Jason Gunthorpe [this message]
[not found] ` <20170608163020.GA16857-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-11 6:51 ` Yishai Hadas
[not found] ` <0ee2641a-4308-6b35-cd0a-e1a5b8b84a6a-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-06-12 16:02 ` Jason Gunthorpe
[not found] ` <20170612160257.GA24829-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-13 15:58 ` Alex Rosenbaum
[not found] ` <CAFgAxU88cfMu7fe9J4Tu=8OFwnND6UfCKF=xi7ZaNHStFpQJog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-13 19:21 ` Jason Gunthorpe
2017-06-08 13:15 ` [PATCH rdma-next V2 4/6] IB/mlx5: Add multicast flow steering support for underlay QP Leon Romanovsky
2017-06-08 13:15 ` [PATCH rdma-next V2 5/6] net/mlx5: Report enhanced capabilities for IPoIB Leon Romanovsky
2017-06-08 13:15 ` [PATCH rdma-next V2 6/6] IB/mlx5: Report RX checksum " Leon Romanovsky
2017-07-28 18:24 ` [PATCH rdma-next V2 0/6] Enable flow steering on IPoIB UD QP Doug Ledford
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=20170608163020.GA16857@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox