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 REPOST 00/10] Hardware tag matching support
Date: Thu, 24 Aug 2017 16:53:50 -0400 [thread overview]
Message-ID: <1503608030.78641.57.camel@redhat.com> (raw)
In-Reply-To: <1503605434.78641.41.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Thu, 2017-08-24 at 16:10 -0400, Doug Ledford wrote:
> On Thu, 2017-08-24 at 15:56 -0400, Doug Ledford wrote:
> > On Thu, 2017-08-17 at 15:52 +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
> >
> > I know in the previous thread on this submission that you thought
> > it
> > didn't need the shared pull request, but I'm seeing this when I try
> > to
> > build after pulling this patch series in:
> > In file included from ./include/linux/mlx5/driver.h:49:0,
> > from ./include/linux/mlx5/fs.h:36,
> > from drivers/infiniband/hw/mlx5/qp.c:37:
> > drivers/infiniband/hw/mlx5/qp.c: In function ‘create_qp_common’:
> > drivers/infiniband/hw/mlx5/qp.c:1734:6: error:
> > ‘MLX5_QPC_OFFLOAD_TYPE_RNDV’ undeclared (first use in this
> > function);
> > did you mean ‘MLX5_XRQC_OFFLOAD_RNDV’?
> > MLX5_QPC_OFFLOAD_TYPE_RNDV);
>
> Nevermind. This is an ordering issue. I took this before your 24
> patch series and I think that is the source of the problem.
Nope, that didn't fix it either. Maybe it needs one of your other
patchsets? I also tried it on the shared code base an it fails to
build there in the same way.
--
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-24 20:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 12:52 [pull request][rdma-next v1 REPOST 00/10] Hardware tag matching support Leon Romanovsky
[not found] ` <20170817125212.3173-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-08-17 12:52 ` [rdma-next v1 REPOST 01/10] IB/core: Add XRQ capabilities Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 02/10] IB/core: Separate CQ handle in SRQ context Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 03/10] IB/core: Add new SRQ type IB_SRQT_TM Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 04/10] IB/uverbs: Add XRQ creation parameter to UAPI Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 05/10] IB/uverbs: Add new SRQ type IB_SRQT_TM Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 06/10] IB/uverbs: Expose XRQ capabilities Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 07/10] IB/mlx5: Fill " Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 08/10] net/mlx5: Add XRQ support Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 09/10] IB/mlx5: Support IB_SRQT_TM Leon Romanovsky
2017-08-17 12:52 ` [rdma-next v1 REPOST 10/10] Documentation: Hardware tag matching Leon Romanovsky
[not found] ` <20170817125212.3173-11-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-08-21 16:04 ` Jason Gunthorpe
[not found] ` <20170821160437.GD4401-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-08-22 8:28 ` Leon Romanovsky
2017-08-24 19:56 ` [pull request][rdma-next v1 REPOST 00/10] Hardware tag matching support Doug Ledford
[not found] ` <1503604595.78641.39.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-24 20:10 ` Doug Ledford
[not found] ` <1503605434.78641.41.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-24 20:53 ` Doug Ledford [this message]
[not found] ` <1503608030.78641.57.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-27 6:08 ` Leon Romanovsky
[not found] ` <20170827060839.GO1724-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-08-27 6:14 ` Leon Romanovsky
2017-08-29 0:03 ` Doug Ledford
2017-08-29 0:37 ` 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=1503608030.78641.57.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;
as well as URLs for NNTP newsgroup(s).