netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hariprasad Shenai <hariprasad@chelsio.com>
To: Yuval Mintz <Yuval.Mintz@qlogic.com>
Cc: David Miller <davem@davemloft.net>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	netdev <netdev@vger.kernel.org>,
	"nirranjan@chelsio.com" <nirranjan@chelsio.com>,
	"leedom@chelsio.com" <leedom@chelsio.com>,
	"kumaras@chelsio.com" <kumaras@chelsio.com>
Subject: Re: [PATCHv2 net-next 1/3] net: Add provision to specify pf number while assigning VF mac
Date: Tue, 19 Jul 2016 13:10:06 +0530	[thread overview]
Message-ID: <20160719074004.GA29269@hari-Latitude-E5550> (raw)
In-Reply-To: <CO2PR11MB0088CA97ED5A2EC7D964536097250@CO2PR11MB0088.namprd11.prod.outlook.com>

On Fri, Jul 01, 2016 at 04:41:52 +0000, Yuval Mintz wrote:
> > > > Chelsio T4/T5 cards have SR-IOV Capabilities on Physical Functions
> > > > 0..3 and the administrative Driver(cxgb4) attaches to Physical Function 4.
> > > > Each of the Physical Functions 0..3 can support up to 16 Virtual
> > > > Functions. With the current Linux APIs, a 2-Port card would only be
> > > > able to use the Virtual Functions on Physical Functions 0..1 and not
> > > > allow the Virtual Functions on Physical Functions 2..3 to be used since
> > > > there are no Ports 2..3 on a 2-Port card.
> > > >
> > > > Also the current ip commands takes netdev as one of the argument, and
> > > > it assumes a 1-to-1 mapping of Network Ports, Physical Functions and the
> > > > SR-IOV Virtual Functions of those Physical Functions. But it is not
> > > > true in our case and won't work for us.
> > > >
> > > > Added a new argument to specify the PF number associated with the VF, to
> > > > fix this.
> > >
> > > I don't get it - what's the exact definition of 'Physical Function'?
> > > Are we talking PCI functions? Logical partitons? Something else?
> 
> > Its PCIe physical function. Physical functions (PFs) are full-featured
> > PCIe functions; virtual functions (VFs) are "lightweight" functions that
> > lack configuration resource.
> 
> Seems like a bad precedent to me - the control node is always the netdevice.
> While I understand your need, looks like what you really want some kind of
> a dummy netdevice for the higher PFs through which you could control their
> VFs.

Hi Dave and all,

Based on above comment, since the control node should always be net_device, we
will go with the below implementation.

We will have dummy net devices with 00:00:00:00:00:00 mac address. The device
won't be associated with any port, since it doesn't need to transmit/receive.
On a two port adapter, we need to create 4 dummy net devices, corresponding to
PF0 ... PF3. Basically the dummy net device will have  callback's only 
for "ndo_set_vf_*" API's.

Thanks,
Hariprasad Shenai

  parent reply	other threads:[~2016-07-19  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 15:34 [PATCHv2 net-next 0/3] Add option to specify PF parameter for IFLA_VF_MAC Hariprasad Shenai
2016-06-30 15:34 ` [PATCHv2 net-next 1/3] net: Add provision to specify pf number while assigning VF mac Hariprasad Shenai
2016-06-30 19:04   ` Yuval Mintz
2016-07-01  3:10     ` Hariprasad Shenai
     [not found]       ` <CO2PR11MB0088CA97ED5A2EC7D964536097250@CO2PR11MB0088.namprd11.prod.outlook.com>
2016-07-19  7:40         ` Hariprasad Shenai [this message]
2016-06-30 15:34 ` [PATCHv2 net-next 2/3] cxgb4/cxgb4vf: Add set VF mac address support Hariprasad Shenai
2016-06-30 15:34 ` [PATCHv2 net-next iproute2 3/3] ip: Add option to specify PF number associated with the VF Hariprasad Shenai

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=20160719074004.GA29269@hari-Latitude-E5550 \
    --to=hariprasad@chelsio.com \
    --cc=Yuval.Mintz@qlogic.com \
    --cc=davem@davemloft.net \
    --cc=kumaras@chelsio.com \
    --cc=leedom@chelsio.com \
    --cc=netdev@vger.kernel.org \
    --cc=nirranjan@chelsio.com \
    --cc=stephen@networkplumber.org \
    /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).