linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.duyck@gmail.com>
To: Donald Dutile <ddutile@redhat.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
	yuvalmin@broadcom.com, bhutchings@solarflare.com,
	gregory.v.rose@intel.com, davem@davemloft.net
Subject: Re: [RFC v2] PCI: sysfs per device SRIOV control and status
Date: Sat, 06 Oct 2012 11:21:00 -0700	[thread overview]
Message-ID: <5070768C.4030905@gmail.com> (raw)
In-Reply-To: <1349388885-43938-1-git-send-email-ddutile@redhat.com>

On 10/4/2012 3:14 PM, Donald Dutile wrote:
> Provide files under sysfs to determine the max number of vfs
> an SRIOV-capable PCIe device supports, and methods to enable and
> disable the vfs on a per device basis.
>
> Currently, VF enablement by SRIOV-capable PCIe devices is done
> in driver-specific module parameters.  If not setup in modprobe files,
> it requires admin to unload & reload PF drivers with number of desired
> VFs to enable.  Additionally, the enablement is system wide: all
> devices controlled by the same driver have the same number of VFs
> enabled.  Although the latter is probably desired, there are PCI
> configurations setup by system BIOS that may not enable that to occur.
>
> Three files are created if a PCIe device has SRIOV support:
> sriov_max_vfs -- cat-ing this file returns the maximum number
>                   of VFs a PCIe device supports.
> sriov_enable_vfs -- echo'ing a number to this file enables this
>                      number of VFs for this given PCIe device.
>                   -- cat-ing this file will return the number of VFs
>                      currently enabled on this PCIe device.
> sriov_disable_vfs -- echo-ing any number other than 0 disables all
>                       VFs associated with this PCIe device.
>
> VF enable and disablement is invoked much like other PCIe
> configuration functions -- via registered callbacks in the driver,
> i.e., probe, release, etc.
>
> v1->v2:
> This patch is based on previous 2 patches by Yinghai Lu
> that cleaned up the vga attributes for PCI devices under sysfs,
> and uses visibility-checking group attributes as recommended by
> Greg K-H.
>
> Signed-off-by: Donald Dutile <ddutile@redhat.com>

I'm not certain if having separate values/functions for enable and 
disabling VFs will work out very well.  It seems like it would probably 
make more sense just to have one value that manipulates NumVFs.  As is, 
in the sriov_enable_vfs case we would end up having to disable SR-IOV 
should we be changing the number of VFs anyway so it would probably make 
sense to just merge both values into a single one and use 0 as the value 
to disable SR-IOV.

Also in the naming scheme for the values it may preferable to use the 
names of the values from the SR-IOV PCIe capability to avoid any 
confusion on what the values represent.  I believe the names for the two 
values you are representing are TotalVFs and NumVFs.

Thanks,

Alex

  parent reply	other threads:[~2012-10-06 18:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 22:14 [RFC v2] PCI: sysfs per device SRIOV control and status Donald Dutile
2012-10-04 22:30 ` Yinghai Lu
2012-10-04 22:50   ` Don Dutile
2012-10-04 23:05     ` Yinghai Lu
2012-10-05 15:10       ` Don Dutile
2012-10-06 18:21 ` Alexander Duyck [this message]
2012-10-08 15:44   ` Greg Rose
2012-10-09 18:39     ` Don Dutile
2012-10-09 20:31       ` Rose, Gregory V
2012-10-09 22:49         ` Don Dutile
2012-10-24  5:47           ` Yuval Mintz
2012-10-25 13:19             ` Don Dutile
2012-10-09 16:12   ` Don Dutile

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=5070768C.4030905@gmail.com \
    --to=alexander.duyck@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=ddutile@redhat.com \
    --cc=gregory.v.rose@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=yuvalmin@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).