From: Ben Hutchings <bhutchings@solarflare.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: <Narendra_K@dell.com>, <netdev@vger.kernel.org>, <ogerlitz@mellanox.com>
Subject: Re: [RFC PATCH net-next] mlx4_en: Do not set dev_id to port number
Date: Fri, 14 Jun 2013 21:14:42 +0100 [thread overview]
Message-ID: <1371240882.1940.18.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <CAJZOPZLv9aidr7fV_2ntqy1DeZZGd9yUHZT1Dqbk=w-bssw69Q@mail.gmail.com>
On Fri, 2013-06-14 at 22:55 +0300, Or Gerlitz wrote:
> On Fri, Jun 14, 2013 at 6:06 PM, <Narendra_K@dell.com> wrote:
> > Port number should not be stored in dev_id. 'dev_id' field was
> > intended to be used to differentiate between multiple devices
> > which share the same MAC address.
>
> Maybe you want to say that dev_id is **now** intended to differentiate
> between multiple devices which share the same MAC address?
That was the original intent but it wasn't well-documented. (Hence
several of us driver writers have made a similar mistake.)
> the reason that mlx4_en and IPoIB use this field is
>
> 1. the Mellanox exposes one PCI function but has two ports with a
> netdevice set on each
>
> 2. there was no standard way to expose the port number used by two
> netdevices that share the same PCI function
>
> 3. here http://patchwork.ozlabs.org/patch/53547/ we were suggested by
> the netdev maintainers to use that field
>
> This patch introduces a regression and can't get in without a
> replacment mechanism.
If you have userland tools relying on this then I agree it should be
left alone, but maybe add a comment explaining why the field is used in
an unusual way.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-06-14 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 15:06 [RFC PATCH net-next] mlx4_en: Do not set dev_id to port number Narendra_K
2013-06-14 19:55 ` Or Gerlitz
2013-06-14 20:14 ` Ben Hutchings [this message]
2013-06-14 20:18 ` Or Gerlitz
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=1371240882.1940.18.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=Narendra_K@dell.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=or.gerlitz@gmail.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