netdev - Re: [PATCH net-next] net: Add phys_port identifier to struct net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1374418103.16533.69.camel@deadeye.wl.decadent.org.uk>
Date:	Sun, 21 Jul 2013 15:48:23 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Or Gerlitz <or.gerlitz@...il.com>
CC:	Jiri Pirko <jiri@...nulli.us>, <Narendra_K@...l.com>,
	<netdev@...r.kernel.org>, <john.r.fastabend@...el.com>
Subject: Re: [PATCH net-next] net: Add phys_port identifier to struct
 net_device and export it to sysfs

On Sun, 2013-07-21 at 14:14 +0300, Or Gerlitz wrote:
> On Sun, Jul 21, 2013 at 10:24 AM, Jiri Pirko <jiri@...nulli.us> wrote:
> [...]
> 
> Sorry, I missed that fact that initially you responded on this thread
> 
> > The value could be anything. But note that you have to have different
> > values for card1-port1,2 and card2-port1,2
> 
> why?

The intent is to identify physical ports uniquely, so userland can tell
whether two devices are backed by the same physical port.

But there's no requirement on the format, so you could ensure that one
byte of this identifier is the port number on the board.

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