From: Matt Domsch <Matt_Domsch@dell•com>
To: Dmitry Kravkov <dmitry@broadcom•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org,
Eilon Greenstein <eilong@broadcom•com>,
narendra_k@dell•com, jordan_hargrave@dell•com
Subject: Re: [PATCH net-next] bnx2x: Add Nic partitioning mode (57712 devices)
Date: Mon, 29 Nov 2010 00:01:14 -0600 [thread overview]
Message-ID: <20101129060114.GC29904@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <1290982177.6066.3.camel@lb-tlvb-dmitry>
On Mon, Nov 29, 2010 at 12:09:37AM +0200, Dmitry Kravkov wrote:
> NIC partitioning is another flavor of multi function - having few
> PCI functions share the same physical port. Unlike the currently
> supported mode of multi-function which depends on the switch
> configuration and uses outer-VLAN, the NPAR mode is switch independent
> and uses the MAC addresses to distribute incoming packets to the different
> functions. This patch adds the specific HW setting of the NPAR mode
> and some distinctions between switch dependent (SD) and
> switch independent (SI) multi-function (MF) modes where the configuration
> is not the same.
Just as SR-IOV introduced sysfs pointers between VF and PF devices:
/sys/bus/pci/devices/pci0000:00/0000:00:09.0/0000:05:00.0/virtfn0 -> ../0000:05:10.0/
/sys/bus/pci/devices/pci0000:00/0000:00:09.0/0000:05:10.0/physfn -> ../0000:05:00.0/
I would like to see a similar relationship exposed in sysfs for NPAR
partitions and their respective ports. This will let biosdevname
accurately name NPAR devices according to the scheme:
pci<slot>#<port>_<virtual function>
just as it does for SR-IOV devices. Is there one parent partition
that the child partitions could point back to, or other way to group
all the partitions of a single port?
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
next prev parent reply other threads:[~2010-11-29 6:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 22:09 [PATCH net-next] bnx2x: Add Nic partitioning mode (57712 devices) Dmitry Kravkov
2010-11-29 6:01 ` Matt Domsch [this message]
2010-11-29 9:33 ` Eilon Greenstein
2010-12-06 17:35 ` Matt Domsch
2010-12-06 18:21 ` Dimitris Michailidis
2010-12-09 14:49 ` Eilon Greenstein
2010-12-17 2:45 ` Matt Domsch
2010-12-17 13:22 ` Ben Hutchings
2010-12-19 5:57 ` Matt Domsch
2010-12-19 21:21 ` Ben Hutchings
2010-12-17 23:13 ` Dimitris Michailidis
2010-12-19 5:49 ` Matt Domsch
2010-12-20 19:44 ` Dimitris Michailidis
2011-01-06 14:40 ` Eilon Greenstein
2010-12-01 20:40 ` David Miller
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=20101129060114.GC29904@auslistsprd01.us.dell.com \
--to=matt_domsch@dell$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dmitry@broadcom$(echo .)com \
--cc=eilong@broadcom$(echo .)com \
--cc=jordan_hargrave@dell$(echo .)com \
--cc=narendra_k@dell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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