From: "Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>,
"Walker, Benjamin" <benjamin.walker@intel.com>
Cc: "Howell, Seth" <seth.howell@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"monis@mellanox.com" <monis@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"dledford@redhat.com" <dledford@redhat.com>
Subject: RE: [PATCH] rdma: move the ib_wr_opcode enum to include/uapi
Date: Wed, 19 Sep 2018 23:03:04 +0000 [thread overview]
Message-ID: <13AA599688F47243B14FCFCCC2C803BB4BDC4DE4@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <20180917224743.GG11367@ziepe.ca>
Hi Jason,
> > What is the correct way for a user space application to check whether
> > a NIC supports SEND_WITH_INVAL? We are currently examining the
> > device_cap_flags in the structure returned by ibv_query_device.
> > Specifically, we're looking at IBV_DEVICE_MEM_MGT_EXTENSIONS.
> However,
> > for i40iw, that flag is set. I'm concerned that the feature support
> > flags are common between user space and the kernel, but the actual
> support differs in this case.
>
> That is the correct thing to do. Sadly the i40iw driver is broken, it should be
> fixed to either mask those flags or implement the functionality.
>
A fix to add SEND_WITH_INVAL support to the user space i40iw is coming.
It is currently in regression testing.
Thank you,
Tatyana
> Jason
next prev parent reply other threads:[~2018-09-19 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 22:33 [PATCH] rdma: move the ib_wr_opcode enum to include/uapi Seth Howell
2018-08-15 22:50 ` Jason Gunthorpe
2018-08-15 23:27 ` Howell, Seth
2018-08-16 18:01 ` Jason Gunthorpe
2018-08-20 21:32 ` Howell, Seth
2018-09-17 20:38 ` Walker, Benjamin
2018-09-17 21:08 ` Jason Gunthorpe
2018-09-17 22:29 ` Walker, Benjamin
2018-09-17 22:47 ` Jason Gunthorpe
2018-09-19 23:03 ` Nikolova, Tatyana E [this message]
2018-09-17 23:08 ` Jason Gunthorpe
2018-09-17 23:14 ` Howell, Seth
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=13AA599688F47243B14FCFCCC2C803BB4BDC4DE4@FMSMSX103.amr.corp.intel.com \
--to=tatyana.e.nikolova@intel.com \
--cc=benjamin.walker@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--cc=seth.howell@intel.com \
/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).