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]

Message-ID: <1368113074.2653.2.camel@bwh-desktop.uk.solarflarecom.com>
Date:	Thu, 9 May 2013 16:24:34 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Or Gerlitz <ogerlitz@...lanox.com>
CC:	<netdev@...r.kernel.org>, <amirv@...lanox.com>,
	<ronye@...lanox.com>
Subject: Re: [PATCH RFC 0/2] Control VF link state

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.

Perhaps the default should also be specified?

Ben.

> Disable - VF link state is down and the VF can't send/recv, e.g can be 
>   	  used to suspend the link while configuring the VF.
[...]

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
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