[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110110084700.17798894@nehalam>
Date: Mon, 10 Jan 2011 08:47:00 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: Vlad Dogaru <ddvlad@...edu.org>
Cc: netdev@...r.kernel.org, jamal <hadi@...erus.ca>,
Octavian Purdila <opurdila@...acom.com>
Subject: Re: [PATCH 0/3] iproute2: ip link: add support for network device
groups
On Mon, 10 Jan 2011 13:39:16 +0200
Vlad Dogaru <ddvlad@...edu.org> wrote:
> This patch series adds userspace support for network device groups.
> There is support for setting device groups, listing only interfaces of a
> specific group, and setting basic device parameters for all interfaces
> in a group.
>
> The patches use the IFLA_GROUP and IFLA_FILTERGROUP messages, for which
> I posted pathes in a different set.
>
>
> Vlad Dogaru (3):
> ip link: add support for setting device groups
> ip link: support listing devices by group
> ip link: support setting device parameters by group
>
> include/linux/if_link.h | 3 ++
> include/linux/netdevice.h | 2 +-
> include/utils.h | 3 +-
> ip/ipaddress.c | 14 +++++++++++
> ip/iplink.c | 54 +++++++++++++++++++++++++++++++++++++++++++-
> ip/link_veth.c | 3 +-
> 6 files changed, 74 insertions(+), 5 deletions(-)
I like the idea, but I wonder if we should take it farther?
Should it be hierarchal tree of groups?
Should slave devices (ppp, vlan, etc) be automatically assigned
to group of parent?
--
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