[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201007230935.59010.leedom@chelsio.com>
Date: Fri, 23 Jul 2010 09:35:58 -0700
From: Casey Leedom <leedom@...lsio.com>
To: Stefan Assmann <sassmann@...hat.com>
Cc: "Rose, Gregory V" <gregory.v.rose@...el.com>,
David Miller <davem@...emloft.net>, shemminger@...tta.com,
andy@...yhouse.net, harald@...hat.com, bhutchings@...arflare.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
gospo@...hat.com,
"Duyck, Alexander H" <alexander.h.duyck@...el.com>
Subject: Re: [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address
| From: Stefan Assmann <sassmann@...hat.com>
| Date: Friday, July 23, 2010 01:08 am
|
| On 23.07.2010 02:26, Casey Leedom wrote:
| > Or you simply don't have the VF Driver loaded in the "Domain 0" Control
| > OS. When we install the cxgb4 PF Driver with "num_vf=..." this enables
| > the PCI-E SR-IOV Capabilities within the various PFs and the
| > corresponding VF PCI Devices are instantiated and discovered by the
| > Domain 0 Linux OS. But without a cxgb4vf VF Driver loaded, those
| > devices just sit there available for "Device Assignment" to VMs.
|
| Just out of curiosity, how do you prevent the VF driver from getting
| loaded in the host? Except from blacklisting it.
I don't install them. :-)
I'm actually fairly unfamiliar with the details of managing/administering
Linux systems so I'm guessing that there are much better ways of controlling for
which devices a Linux system will attempt to load drivers. For instance, I
didn't know about the concept of "blacklisting" a driver.
Casey
--
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
Powered by blists - more mailing lists