From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>, linux-rdma@vger.kernel.org
Subject: Re: Move the definitions for rxe_av.network_type to uAPI
Date: Fri, 16 Oct 2020 15:20:50 -0500 [thread overview]
Message-ID: <96dfe365-bd38-4022-8019-e337f168af47@gmail.com> (raw)
Jason,
Your recent commit:
commit e0d696d201dd5d31813787d9b61a42fc459eee89
Author: Jason Gunthorpe <jgg@ziepe.ca>
Date: Thu Oct 15 20:42:18 2020 -0300
RDMA/rxe: Move the definitions for rxe_av.network_type to uAPI
has some problems and so far I am having trouble making it work sensibly.
What you have done is to make the network_type field in rxe_av be private,
(i.e. RXE_NETWORK_TYPE_XXX instead of RDMA_NETWORK_XXX). You then defined these
private enums in rdma_uverbs_rxe.h. The problem is that there are more than one
source of AVs those:
passed in user space send WQEs for UD traffic
passed from kernel ULPs for UD traffic
stored in the primary AV in QPs
The AVs created in the kernel get set by calling rdma_gid_attr_network_type()
which returns RDMA_NETWORK_XXX not RXE_NETWORK_TYPE_XXX. This can be fixed by
again making them the same, which you didn't do, but that means they really aren't
private. Or, we can explicitly translate between them in the AV init code.
No rush but I still think the right answer is to let user space only have to deal
with AHs and not AVs.
There was also a confusion between V6 and V4. I will submit a small patch that
fixes that and makes the enums the same again which is more efficient than transocding
them.
Bob
next reply other threads:[~2020-10-16 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:20 Bob Pearson [this message]
2020-10-16 20:31 ` Move the definitions for rxe_av.network_type to uAPI 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=96dfe365-bd38-4022-8019-e337f168af47@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.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 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.