From: Stefan Assmann <sassmann@redhat.com>
To: Casey Leedom <leedom@chelsio.com>
Cc: "Rose, Gregory V" <gregory.v.rose@intel.com>,
David Miller <davem@davemloft.net>,
shemminger@vyatta.com, andy@greyhouse.net, harald@redhat.com,
bhutchings@solarflare.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, gospo@redhat.com, "Duyck,
Alexander H" <alexander.h.duyck@intel.com>
Subject: Re: [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address
Date: Fri, 23 Jul 2010 10:08:14 +0200 [thread overview]
Message-ID: <4C494DEE.3010101@redhat.com> (raw)
In-Reply-To: <2408F875-69BE-45D3-8605-4AE5CDA4601C@chelsio.com>
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 \x13 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.
Stefan
--
Stefan Assmann | Red Hat GmbH
Software Engineer | Otto-Hahn-Strasse 20, 85609 Dornach
| HR: Amtsgericht Muenchen HRB 153243
| GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com | Michael Cunningham, Charles Cachera
next prev parent reply other threads:[~2010-07-23 8:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 10:50 [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address Stefan Assmann
2010-07-20 11:20 ` Ben Hutchings
2010-07-20 11:47 ` Stefan Assmann
2010-07-20 11:58 ` Alex Badea
2010-07-20 12:17 ` Stefan Assmann
2010-07-20 20:18 ` David Miller
2010-07-21 8:10 ` Stefan Assmann
2010-07-21 13:54 ` Ben Hutchings
2010-07-22 12:50 ` [PATCH net-next] sysfs: add attribute to indicate hw address assignment type Stefan Assmann
2010-07-22 14:07 ` Ben Hutchings
2010-07-22 14:47 ` Stefan Assmann
2010-07-25 3:50 ` David Miller
2010-07-20 12:07 ` [PATCH net-next] sysfs: add entry to indicate network interfaces with random MAC address Ben Hutchings
2010-07-20 12:41 ` Stefan Assmann
2010-07-20 14:29 ` Ben Hutchings
2010-07-20 20:17 ` David Miller
2010-07-20 21:18 ` Stephen Hemminger
2010-07-20 21:20 ` David Miller
2010-07-21 6:26 ` Harald Hoyer
2010-07-21 6:34 ` David Miller
2010-07-21 6:47 ` Harald Hoyer
2010-07-21 15:07 ` Andy Gospodarek
2010-07-21 16:34 ` Casey Leedom
2010-07-21 17:28 ` Stephen Hemminger
2010-07-21 17:32 ` David Miller
2010-07-21 18:29 ` Casey Leedom
2010-07-21 18:39 ` David Miller
2010-07-21 19:25 ` Casey Leedom
2010-07-21 18:43 ` Rose, Gregory V
2010-07-21 18:48 ` David Miller
2010-07-21 18:50 ` David Miller
2010-07-21 19:02 ` Rose, Gregory V
2010-07-21 19:33 ` David Miller
2010-07-21 19:35 ` Rose, Gregory V
2010-07-22 7:12 ` Ian Campbell
2010-07-22 6:53 ` Stefan Assmann
2010-07-23 0:26 ` Casey Leedom
2010-07-23 8:08 ` Stefan Assmann [this message]
2010-07-23 16:35 ` Casey Leedom
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=4C494DEE.3010101@redhat.com \
--to=sassmann@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=gregory.v.rose@intel.com \
--cc=harald@redhat.com \
--cc=leedom@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.