From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Xiao Yang <yangx.jy@fujitsu.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-core] libibverbs/examples: Add missing device attributes
Date: Fri, 11 Feb 2022 08:41:39 -0400 [thread overview]
Message-ID: <20220211124139.GL4160@nvidia.com> (raw)
In-Reply-To: <YgOCXCXWyCTxvva8@unreal>
On Wed, Feb 09, 2022 at 10:59:08AM +0200, Leon Romanovsky wrote:
> On Wed, Feb 09, 2022 at 10:53:08AM +0800, Xiao Yang wrote:
> > make ibv_devinfo command show more device attributes.
> >
> > Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
> > libibverbs/examples/devinfo.c | 29 +++++++++++++++++++++++++----
> > libibverbs/verbs.h | 13 ++++++++++---
> > 2 files changed, 35 insertions(+), 7 deletions(-)
>
> I have a feeling that a long time ago, we had a discussion if and how
> expose device capabilities and the decision was that we don't report
> in-kernel specific device caps.
Right, it is kernel bug they leak out in the first place.
> > diff --git a/libibverbs/verbs.h b/libibverbs/verbs.h
> > index a9f182ff..68591c7b 100644
> > +++ b/libibverbs/verbs.h
> > @@ -136,7 +136,9 @@ enum ibv_device_cap_flags {
> > IBV_DEVICE_MEM_WINDOW_TYPE_2B = 1 << 24,
> > IBV_DEVICE_RC_IP_CSUM = 1 << 25,
> > IBV_DEVICE_RAW_IP_CSUM = 1 << 26,
> > - IBV_DEVICE_MANAGED_FLOW_STEERING = 1 << 29
> > + IBV_DEVICE_CROSS_CHANNEL = 1 << 27,
> > + IBV_DEVICE_MANAGED_FLOW_STEERING = 1 << 29,
> > + IBV_DEVICE_INTEGRITY_HANDOVER = 1 << 30
> > };
> >
> > enum ibv_fork_status {
> > @@ -149,8 +151,13 @@ enum ibv_fork_status {
> > * Can't extended above ibv_device_cap_flags enum as in some systems/compilers
> > * enum range is limited to 4 bytes.
> > */
> > -#define IBV_DEVICE_RAW_SCATTER_FCS (1ULL << 34)
> > -#define IBV_DEVICE_PCI_WRITE_END_PADDING (1ULL << 36)
> > +#define IBV_DEVICE_ON_DEMAND_PAGING (1ULL << 31)
> > +#define IBV_DEVICE_SG_GAPS_REG (1ULL << 32)
> > +#define IBV_DEVICE_VIRTUAL_FUNCTION (1ULL << 33)
> > +#define IBV_DEVICE_RAW_SCATTER_FCS (1ULL << 34)
> > +#define IBV_DEVICE_RDMA_NETDEV_OPA (1ULL << 35)
> > +#define IBV_DEVICE_PCI_WRITE_END_PADDING (1ULL << 36)
> > +#define IBV_DEVICE_ALLOW_USER_UNREG (1ULL << 37)
And don't copy ABI into header like this, the kernel parts need to be
moved to the kernel uabi header and cleaned
Jason
next prev parent reply other threads:[~2022-02-11 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 2:53 [PATCH rdma-core] libibverbs/examples: Add missing device attributes Xiao Yang
2022-02-09 8:59 ` Leon Romanovsky
2022-02-11 12:41 ` Jason Gunthorpe [this message]
2022-03-07 10:03 ` yangx.jy
2022-03-09 13:20 ` 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=20220211124139.GL4160@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yangx.jy@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.