[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1383088365.16822.22.camel@sakura.staff.proxad.net>
Date: Wed, 30 Oct 2013 00:12:45 +0100
From: Maxime Bizon <mbizon@...ebox.fr>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Felix Fietkau <nbd@...nwrt.org>,
Florian Fainelli <f.fainelli@...il.com>,
Neil Horman <nhorman@...driver.com>,
John Fastabend <john.r.fastabend@...el.com>,
netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Sascha Hauer <s.hauer@...gutronix.de>,
John Crispin <blogic@...nwrt.org>,
Jonas Gorski <jogo@...nwrt.org>,
Gary Thomas <gary@...assoc.com>,
Vlad Yasevich <vyasevic@...hat.com>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: [PATCH 1/4 net-next] net: phy: add Generic Netlink Ethernet
switch configuration API
On Wed, 2013-10-23 at 08:53 -0400, Jamal Hadi Salim wrote:
> So exposing the 5-8 ports as netdevs would be useful. Giving access to
> their stats through per-port netdevs etc. i.e a switch/bridge will
While the intent is to make it look familiar to users, IMO this breaks
the rule of the least surprise.
>From a user POV, when you see a netdevice, you expect to be able to
receive or send packets from/to it. The ability to read stats/link is
only a secondary feature.
Wireless subsystem moved away from using dummy/additional netdevices
because it caused confusion.
multiqueue devices forced us to separate struct netdevice and struct
netdev_queue, maybe it's time for more surgery :)
--
Maxime
--
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