From: "Íñigo Huguet" <ihuguet@redhat.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ivan Vecera <ivecera@redhat.com>,
Edward Harold Cree <ecree@xilinx.com>,
Dinan Gunawardena <dinang@xilinx.com>,
Pablo Cascon <pabloc@xilinx.com>
Subject: Re: Correct interpretation of VF link-state=auto
Date: Mon, 21 Jun 2021 17:12:25 +0200 [thread overview]
Message-ID: <CACT4oufCHsXLsw4uLtYMD4d3_UvJYn_Nr1dbiGYvPRVz=fwnNA@mail.gmail.com> (raw)
In-Reply-To: <9a0836b2f5ed487bb7d9c03a4b17222f@intel.com>
On Fri, Jun 18, 2021 at 6:35 PM Jakub Kicinski <kuba@kernel.org> wrote:
> Like all legacy SR-IOV networking the correct thing to do here is clear
> as mud. I'd go for the link status of the PF netdev. If the netdev
> cannot pass traffic (either for administrative or physical link reasons)
> then VFs shouldn't talk either. But as I said, every vendor will have their
> own interpretation, and different users may expect different things...
On Fri, Jun 18, 2021 at 9:10 PM Keller, Jacob E
<jacob.e.keller@intel.com> wrote:
> I like this interpretation too.. but I agree that it's unfortunately confusing and each vendor has done something different.. :(
Thanks Jakub and Keller, at least now it's clear that it's not clear :P
Good enough info to move forward, for me.
--
Íñigo Huguet
prev parent reply other threads:[~2021-06-21 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:34 Correct interpretation of VF link-state=auto Íñigo Huguet
2021-06-18 15:21 ` Íñigo Huguet
2021-06-18 16:35 ` Jakub Kicinski
2021-06-18 19:10 ` Keller, Jacob E
2021-06-21 15:12 ` Íñigo Huguet [this message]
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='CACT4oufCHsXLsw4uLtYMD4d3_UvJYn_Nr1dbiGYvPRVz=fwnNA@mail.gmail.com' \
--to=ihuguet@redhat.com \
--cc=dinang@xilinx.com \
--cc=ecree@xilinx.com \
--cc=ivecera@redhat.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabloc@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).