From: Jason Gunthorpe <jgg@nvidia.com>
To: liweihang <liweihang@huawei.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: Question about the mechanism of RoCEv2 VLAN validation
Date: Thu, 28 Jan 2021 10:11:36 -0400 [thread overview]
Message-ID: <20210128141136.GF4247@nvidia.com> (raw)
In-Reply-To: <ff917571dbae45fe9c9d840bac400404@huawei.com>
On Thu, Jan 28, 2021 at 02:08:21PM +0000, liweihang wrote:
> UD is connectionless-oriented, an UD QP won't record VLAN info in it's QPC,
> so how to achieve the checking mechanism? Or a UD QP should just ignore the
> unmatched VLAN ID?
Right, UD QPs recieve all packets for the entire device that match the
UD QPN
They indirectly report the incoming gid table index they were matched
with in the completion and the first 40 bytes
If an app only wants to look at certain gid table entries then it is
up to the app to filter
Jason
next prev parent reply other threads:[~2021-01-28 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 14:08 Question about the mechanism of RoCEv2 VLAN validation liweihang
2021-01-28 14:11 ` Jason Gunthorpe [this message]
2021-01-29 1:21 ` liweihang
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=20210128141136.GF4247@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liweihang@huawei.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.