[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXQj_KdWT-mVVsptxiEgGjScgDy_Lp-aXioZ4YAQh1wWQ@mail.gmail.com>
Date: Wed, 19 Sep 2012 15:17:31 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Ben Hutchings <bhutchings@...arflare.com>,
Bjorn Helgaas <bhelgaas@...gle.com>
Cc: 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 12:44 PM, Ben Hutchings
<bhutchings@...arflare.com> wrote:
> On Wed, 2012-09-19 at 08:53 -0700, Greg Rose wrote:
>> I was not able to attend the Linux conference held at the end of August
>> myself but coworkers of mine here at Intel informed that method 2 here
>> seems to be the preferred approach. Perhaps some folks who attended
>> the the conference can chime in with more specifics.
>
> There really wasn't much more specific discussion. Bjorn's summary of
> the mini-summit <http://lwn.net/Articles/514113/> says:
>
>> SR-IOV Management
>>
>> Currently drivers implement module parameters like "max_vfs". This means
>> all devices claimed by the driver get the same number of VFs, and you can't
>> change anything without unloading and reloading the driver.
>>
>> Consensus that we should try to implement a knob for this in sysfs so it
>> can be generic (not in each driver) and set individually for each device.
>
> I don't think any implementation has been posted to the linux-pci list
please check attached three patches...
Thanks
Yinghai
Download attachment "pci_dev_type.patch" of type "application/octet-stream" (2042 bytes)
Download attachment "pci_010_pci_dev_boot_vga_x.patch" of type "application/octet-stream" (1868 bytes)
Download attachment "sriov_xxx.patch" of type "application/octet-stream" (2158 bytes)
Powered by blists - more mailing lists