All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Eilon Greenstein <eilong@broadcom.com>,
	Dimitris Michailidis <dm@chelsio.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: Sat, 18 Dec 2010 23:57:31 -0600	[thread overview]
Message-ID: <20101219055731.GD5854@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <1292592157.3136.819.camel@localhost>

On Fri, Dec 17, 2010 at 01:22:37PM +0000, Ben Hutchings wrote:
> On Thu, 2010-12-16 at 20:45 -0600, Matt Domsch wrote:
> > On Thu, Dec 09, 2010 at 04:49:25PM +0200, Eilon Greenstein wrote:
> In the case of sfc, each port has a separate PCI function.  We read this
> register field to find out which port we're talking to, as
> virtualisation can alter the function number.  I don't know about the
> others.

For a single card then, this makes sense.

pci<slot>#<port>  where port = dev_id

If I have 2 such cards on a PCI extender though, I think this breaks.
Here, I'd see duplicate dev_id values, yes?

Do you label the ports on your cards in any fashion?  Do they have
labels like port 0, port 1, port 2, ... ?  Does it matter if we give
names starting at 0, or starting at 1?  latest biosdevname starts them
at 1, or uses whatever value BIOS actually provides, which on systems
I've tried, all start at 1.

Maybe the PCI extender case I should just ignore as being unsolvable
right now...  If I think N PCI devices are in the same slot, then
using the dev_id value as a per-slot value is fine.  If there's an
extender that would break this scheme, biosdevname now returns nothing
for any names it would otherwise suggest duplicate names for,
essentially throwing its hands up "I don't know".

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO

  reply	other threads:[~2010-12-19  5:57 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
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 [this message]
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=20101219055731.GD5854@auslistsprd01.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=dm@chelsio.com \
    --cc=dmitry@broadcom.com \
    --cc=eilong@broadcom.com \
    --cc=jordan_hargrave@dell.com \
    --cc=narendra_k@dell.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.