netdev - RE: Generic interface to make physical port number used by a netdevice available to user space

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <E31FB011129F30488D5861F383904915210B96144A@BLRX7MCDC201.AMER.DELL.COM>
Date:	Mon, 27 May 2013 18:39:00 +0530
From:	<Narendra_K@...l.com>
To:	<stephen@...workplumber.org>
CC:	<netdev@...r.kernel.org>
Subject: RE: Generic interface to make physical port number used by a
 netdevice available to user space

> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@...workplumber.org]
> Sent: Thursday, May 23, 2013 10:04 PM
> To: K, Narendra
> Cc: netdev@...r.kernel.org
> Subject: Re: Generic interface to make physical port number used by a
> netdevice available to user space
> 
> On Wed, 22 May 2013 13:24:15 +0530
> <Narendra_K@...l.com> wrote:
> > It would be great to know list's thoughts on  'dev_id' being used as
> > the interface to make the physical port number information used by
> > netdevice available to user space or do we need a new sysfs attribute for
> the same.
> >
> > Note: I think in the scenario of SRIOV VF devices assigned to guest
> > and being bonded, additional information would be needed to
> > differentiate the network controller in the host.  But I suppose it is a
> different problem than this.
> >
> > References to related discussions:
> > 1. [PATCH net-next] bnx2x: Add Nic partitioning mode (57712)
> > http://marc.info/?l=linux-netdev&m=129098288709528&w=2
> > 2. [PATCH net-next] bonding: Support for multi function NIC devices
> > http://marc.info/?l=linux-netdev&m=134240221118594&w=2
> >
> > Thank you,
> >
> 
> One idea would be to reuse the mostly outdated if_port field.
> As far as I can see only drivers using it are legacy drivers which support AUI vs.
> TP back in the old bad days of BNC Ethernet.

Hi Stephen, thank you.

I think if_port or dev_id would be fine. The difference seems to be  that dev_id is already exported to sysfs.

With regards,
Narendra K
Linux Engineering
Dell Inc.
 


--
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