From: Dimitris Michailidis <dm@chelsio•com>
To: Matt Domsch <Matt_Domsch@dell•com>
Cc: Eilon Greenstein <eilong@broadcom•com>,
Dmitry Kravkov <dmitry@broadcom•com>,
"davem@davemloft•net" <davem@davemloft•net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"narendra_k@dell•com" <narendra_k@dell•com>,
"jordan_hargrave@dell•com" <jordan_hargrave@dell•com>
Subject: Re: [PATCH net-next] bnx2x: Add Nic partitioning mode (57712 devices)
Date: Mon, 06 Dec 2010 10:21:50 -0800 [thread overview]
Message-ID: <4CFD29BE.2060201@chelsio.com> (raw)
In-Reply-To: <20101206173534.GC13628@auslistsprd01.us.dell.com>
Matt Domsch wrote:
> For SR-IOV, biosdevname follows the physfn and virtfn* pointers to map
> VFs to the PF.
This gives the PF a VF maps to but in general doesn't say anything about the
port the VF maps to, unless you make additional assumptions as below.
> But it assumes 1 PF -> 1 port. For the Intel 1GbE and
> 10GbE cards I have, this is true, but nothing says it has to be true.
Yes, there are devices for which this isn't true. You can have several PFs
mapping to 1 port, 1 PF mapping to several ports, a PF mapping to some
port(s) but its VFs mapping to different port(s), ...
> Maybe something like:
>
> /sys/class/net_port/<port_name>/<ifname> -> /sys/class/net/<ifname>
>
> /sys/class/net/<ifname>/port -> /sys/class/net_port/<port_name>
>
> This introduces the idea of ports, though adds the complication of
> needing to name them somehow. But it would expose the relationship of
> each net interface to a specific port, as well as allow multiple
> interfaces per port, conceptually independent of the PCI device
> mapping. That way, each driver, which must know the mapping somehow,
> could fill these links out?
/sys/class/net/<ifname>/dev_id indicates the physical port <ifname> is
associated with. At least a few drivers set up dev_id this way.
next prev parent reply other threads:[~2010-12-06 18:21 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
2010-11-29 9:33 ` Eilon Greenstein
2010-12-06 17:35 ` Matt Domsch
2010-12-06 18:21 ` Dimitris Michailidis [this message]
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=4CFD29BE.2060201@chelsio.com \
--to=dm@chelsio$(echo .)com \
--cc=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