From: Jason Gunthorpe <jgg@nvidia.com>
To: Bryan Tan <bryantan@vmware.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Pv-drivers <Pv-drivers@vmware.com>
Subject: Re: [PATCH for-rc] RDMA/vmw_pvrdma: Fix network_hdr_type reported in WC
Date: Fri, 15 Jan 2021 08:50:31 -0400 [thread overview]
Message-ID: <20210115125031.GY4147@nvidia.com> (raw)
In-Reply-To: <BL0PR05MB501015BAF25CADD722F5A9FCB2A79@BL0PR05MB5010.namprd05.prod.outlook.com>
On Fri, Jan 15, 2021 at 04:58:58AM +0000, Bryan Tan wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Friday, January 15, 2021 1:24 AM
> > On Thu, Jan 14, 2021 at 06:26:48AM -0800, Bryan Tan wrote:
> > > The PVRDMA device defines network_hdr_type according to an old
> > > definition of the rdma_network_type enum that has since changed,
> > > resulting in the wrong rdma_network_type being reported. Fix this by
> > > explicitly defining the enum used by the PVRDMA device and adding a
> > > function to convert the pvrdma_network_type to rdma_network_type enum.
> >
> > How come I can't find anything reading this in rdma-core?
> >
> > $ ~/oss/rdma-core#git grep network_hdr_type
> > kernel-headers/rdma/vmw_pvrdma-abi.h: __u8 network_hdr_type;
> >
> > ??
>
> network_hdr_type isn't exposed in the userspace WC ibv_wc.
So this is "HW" API then?
> Given that the field is only in the kernel side, it didn't seem like
> we should add the new enum to vmw_pvrdma-abi.h either.
Well, the struct that holds the value is in a uapi header, so the
definition should be too. If you are defining HW data in uapi then may
as well define all of it.
Jason
next prev parent reply other threads:[~2021-01-15 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 14:26 [PATCH for-rc] RDMA/vmw_pvrdma: Fix network_hdr_type reported in WC Bryan Tan
2021-01-14 17:23 ` Jason Gunthorpe
2021-01-15 4:58 ` Bryan Tan
2021-01-15 12:50 ` Jason Gunthorpe [this message]
2021-01-18 11:46 ` Bryan Tan
2021-01-18 13:57 ` Jason Gunthorpe
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=20210115125031.GY4147@nvidia.com \
--to=jgg@nvidia.com \
--cc=Pv-drivers@vmware.com \
--cc=bryantan@vmware.com \
--cc=linux-rdma@vger.kernel.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