[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1371240882.1940.18.camel@bwh-desktop.uk.level5networks.com>
Date: Fri, 14 Jun 2013 21:14:42 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Or Gerlitz <or.gerlitz@...il.com>
CC: <Narendra_K@...l.com>, <netdev@...r.kernel.org>,
<ogerlitz@...lanox.com>
Subject: Re: [RFC PATCH net-next] mlx4_en: Do not set dev_id to port number
On Fri, 2013-06-14 at 22:55 +0300, Or Gerlitz wrote:
> On Fri, Jun 14, 2013 at 6:06 PM, <Narendra_K@...l.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists