netdev - Re: New commands to configure IOV features

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:	Wed, 19 Sep 2012 23:08:02 -0400
From:	Subhendu Ghosh <sghosh151@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ben Hutchings <bhutchings@...arflare.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Greg Rose <gregory.v.rose@...el.com>,
	Yuval Mintz <yuvalmin@...adcom.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Ariel Elior <ariele@...adcom.com>,
	Eilon Greenstein <eilong@...adcom.com>,
	linux-pci <linux-pci@...r.kernel.org>
Subject: Re: New commands to configure IOV features

On Wed, Sep 19, 2012 at 10:27 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Wed, Sep 19, 2012 at 6:23 PM, Ben Hutchings
> <bhutchings@...arflare.com> wrote:
>> On Wed, 2012-09-19 at 17:19 -0700, Yinghai Lu wrote:
>>> could just stop the device and add it back again?
>>
>> This is highly disruptive and I think it would be totally unacceptable
>> for at least networking devices.
>
> so you want PF network device continue work while enable VF on it?
>

Yes - normal scenario a system is installed thru automation over a
network. The default initrd for installer does not configure VFs.
Post install, a management tool like Openstack Quantum or others are
used to enable VFs. If the PF NIC happens to be the communication path
- disrupting the PF during a remote configuration cycle can leave you
blind and the system unreachable.

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