From: Stephen Hemminger <shemminger@vyatta.com>
To: Vlad Dogaru <ddvlad@rosedu.org>
Cc: netdev@vger.kernel.org, jamal <hadi@cyberus.ca>,
Octavian Purdila <opurdila@ixiacom.com>
Subject: Re: [PATCH 0/3] iproute2: ip link: add support for network device groups
Date: Mon, 10 Jan 2011 08:47:00 -0800 [thread overview]
Message-ID: <20110110084700.17798894@nehalam> (raw)
In-Reply-To: <1294659559-22648-1-git-send-email-ddvlad@rosedu.org>
On Mon, 10 Jan 2011 13:39:16 +0200
Vlad Dogaru <ddvlad@rosedu.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?
next prev parent reply other threads:[~2011-01-10 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 11:39 [PATCH 0/3] iproute2: ip link: add support for network device groups Vlad Dogaru
2011-01-10 11:39 ` [PATCH 1/3] ip link: add support for setting " Vlad Dogaru
2011-01-10 11:39 ` [PATCH 2/3] ip link: support listing devices by group Vlad Dogaru
2011-01-10 11:39 ` [PATCH 3/3] ip link: support setting device parameters " Vlad Dogaru
2011-01-10 16:47 ` Stephen Hemminger [this message]
2011-01-11 12:38 ` [PATCH 0/3] iproute2: ip link: add support for network device groups jamal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110110084700.17798894@nehalam \
--to=shemminger@vyatta.com \
--cc=ddvlad@rosedu.org \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).