From: David Miller <firstname.lastname@example.org> To: email@example.com Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [PATCH net-next v4 2/2] ipoib: show VF broadcast address Date: Tue, 18 Jun 2019 10:40:37 -0700 (PDT) Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> From: Doug Ledford <firstname.lastname@example.org> Date: Tue, 18 Jun 2019 13:29:59 -0400 > On Tue, 2019-06-18 at 10:08 -0700, David Miller wrote: >> From: Denis Kirjanov <email@example.com> >> Date: Mon, 17 Jun 2019 10:53:41 +0200 >> >> > in IPoIB case we can't see a VF broadcast address for but >> > can see for PF >> >> I just want to understand why this need to see the VF broadcast >> address is IPoIB specific? > > A VF might or might not have the same security domain (P_Key) as the > parent, and the P_Key is encoded in the broadcast address. In the > event that two vfs or a vf and a pf can't see each other over the IPoIB > network, it is necessary to be able to see the broadcast address in use > by each to make sure they are the same and not that they shouldn't be > able to see each other because they are on different P_Keys and > therefore different broadcast multicast groups. Thanks for explaining. I'll apply these to net-next right now then. Thanks again.
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-17 8:53 [PATCH 1/2] ipoib: correcly show a VF hardware address Denis Kirjanov 2019-06-17 8:53 ` [PATCH 2/2] ipoib: show VF broadcast address Denis Kirjanov 2019-06-17 8:53 ` [PATCH net-next v4 1/2] ipoib: correcly show a VF hardware address Denis Kirjanov 2019-06-17 8:53 ` [PATCH net-next v4 2/2] ipoib: show VF broadcast address Denis Kirjanov 2019-06-18 17:08 ` David Miller 2019-06-18 17:29 ` Doug Ledford 2019-06-18 17:40 ` David Miller [this message] 2019-06-17 18:50 ` [PATCH 1/2] ipoib: correcly show a VF hardware address Doug Ledford
Reply instructions: You may reply publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Netdev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/netdev/0 netdev/git/0.git git clone --mirror https://lore.kernel.org/netdev/1 netdev/git/1.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 netdev netdev/ https://lore.kernel.org/netdev \ email@example.com firstname.lastname@example.org public-inbox-index netdev Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.netdev AGPL code for this site: git clone https://public-inbox.org/ public-inbox