[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <13AA599688F47243B14FCFCCC2C803BB4BDC4DE4@FMSMSX103.amr.corp.intel.com>
Date: Wed, 19 Sep 2018 23:03:04 +0000
From: "Nikolova, Tatyana E" <tatyana.e.nikolova@...el.com>
To: Jason Gunthorpe <jgg@...pe.ca>,
"Walker, Benjamin" <benjamin.walker@...el.com>
CC: "Howell, Seth" <seth.howell@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"monis@...lanox.com" <monis@...lanox.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"dledford@...hat.com" <dledford@...hat.com>
Subject: RE: [PATCH] rdma: move the ib_wr_opcode enum to include/uapi
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
Powered by blists - more mailing lists