netdev - Re: [PATCH RFC 0/2] Control VF link state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 10 May 2013 02:17:33 +0300
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	Or Gerlitz <ogerlitz@...lanox.com>, netdev@...r.kernel.org,
	amirv@...lanox.com, ronye@...lanox.com
Subject: Re: [PATCH RFC 0/2] Control VF link state

On Thu, May 9, 2013 at 6:24 PM, Ben Hutchings <bhutchings@...arflare.com> wrote:
>
> On Wed, 2013-05-08 at 16:45 +0300, Or Gerlitz wrote:
> > Here's a suggestion for API and implementation that lets the admin to
> > configure
> > the link state of the VF / SRIOV eSwitch vPORT. Basically, it has three
> > states
> >
> > Auto -        the VF link state will reflect the PF link state
> >
> > Enable - VF link stat will be always up, traffic from VF to VF can
> >        work even if PF link is down.
>
> It seems like it would be useful to implement these two options on the PF as well.

You mean that PF <--> VF communication on the same node can be made to
work even when the physical link is down? this is a bit problematic to
model/implement I think. Generally speaking it makes things easier to
grasp if PF is considered to be the uplink of the eSwitch whos link is
1:1 as the physical link, but need to think that a bit more.


> Perhaps the default should also be specified?

mmm, not sure if we can require/enforce the same default for all drivers.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html