From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [pull request][rdma-next v1 00/11] Hardware tag matching support
Date: Tue, 22 Aug 2017 16:46:49 -0400 [thread overview]
Message-ID: <1503434809.78641.14.camel@redhat.com> (raw)
In-Reply-To: <20170815085912.10181-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Tue, 2017-08-15 at 11:59 +0300, Leon Romanovsky wrote:
> This patch series adds to Mellanox ConnectX HCA driver support of
> tag matching. It introduces new hardware object eXtended shared
> Receive
> Queue (XRQ), which follows SRQ semantics with addition of extended
> receive buffers topologies and offloads.
>
> This series adds tag matching topology and rendezvouz offload.
>
> Changelog:
> v0->v1:
> * Rebased version, no change
> RFC->v0:
> * Followed after RFC posted on the ML and OFVWG discussions
> * Implements agreed verbs interface
> * Rebased on top of latest version
> * Adding feature description under Documentaion/infiniband
> * In struct ib_srq_init_attr moved CQ outside XRC inner struct.
> * Added max size of the information passed after the RNDV header
> * Added hca_sq_owner HW flag for RNDV QPs
>
> Thanks
>
> ----------------------------------------------------------------
>
> Doug,
>
> Please note that I merged our shared pull request from the mailing
> list before sending this series. Please let me know if something
> needs
> to be redone.
Hi Leon,
Does this patchset require the shared pull request? If so, then that
presents a bit of a problem. My for-next tree is based on -rc2 and
your shared tree is based on -rc4, so pulling your tree will do one of
Linus' dreaded forward merges along with the merge of the code. I can
pull your stuff into a separate branch, but that will prevent things
that modify the core from being merged with things that have already
been taken into for-next.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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-08-22 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 8:59 [pull request][rdma-next v1 00/11] Hardware tag matching support Leon Romanovsky
[not found] ` <20170815085912.10181-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-08-15 8:59 ` [rdma-next v1 01/11] net/mlx5: Update HW layout definitions Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 02/11] IB/core: Add XRQ capabilities Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 03/11] IB/core: Separate CQ handle in SRQ context Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 04/11] IB/core: Add new SRQ type IB_SRQT_TM Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 05/11] IB/uverbs: Add XRQ creation parameter to UAPI Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 06/11] IB/uverbs: Add new SRQ type IB_SRQT_TM Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 07/11] IB/uverbs: Expose XRQ capabilities Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 08/11] IB/mlx5: Fill " Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 09/11] net/mlx5: Add XRQ support Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 10/11] IB/mlx5: Support IB_SRQT_TM Leon Romanovsky
2017-08-15 8:59 ` [rdma-next v1 11/11] Documentation: Hardware tag matching Leon Romanovsky
2017-08-22 20:46 ` Doug Ledford [this message]
[not found] ` <1503434809.78641.14.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-23 5:06 ` [pull request][rdma-next v1 00/11] Hardware tag matching support Leon Romanovsky
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=1503434809.78641.14.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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