From: Patrick McHardy <kaber@trash.net>
To: shemminger@osdl.org
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: [IPROUTE 00/02]: rtnl_link support
Date: Wed, 13 Jun 2007 19:02:32 +0200 (MEST) [thread overview]
Message-ID: <20070613170229.8318.75488.sendpatchset@localhost.localdomain> (raw)
Hi Stephen,
these patches add support for the rtnl_link stuff and VLAN configuration
to iproute. Since the old link configuration was entirely ioctl based and
mixing the two would be really ugly, this patch keeps the old ioctl stuff
guarded by an ifdef (defaults to enabled) and probes for support for
using RTM_NEWLINK. Tested to work properly on both old and patched kernel.
I've added a new -d[etail] flag to ip, the driver specific things are only
printed when it is specified. I did this mainly because I'm not sure how
careful we want to be not to confuse people using sed/awk/... on iproute
output. I would prefer to have the information always shown, but I'll
leave that decision up to you.
Changes since the last post:
- Only call link argument parsing function if arguments are present
- Support xstats dumping
- Add sanitized if_vlan.h file for VLAN flag definition
- Support setting/changing VLAN flags
Please apply, thanks.
include/linux/if_link.h | 47 +++++++
include/linux/if_vlan.h | 61 +++++++++
ip/Makefile | 4
ip/ip.c | 5
ip/ip_common.h | 15 ++
ip/ipaddress.c | 39 ++++++
ip/iplink.c | 311 +++++++++++++++++++++++++++++++++++++++++++++++-
ip/iplink_vlan.c | 184 ++++++++++++++++++++++++++++
8 files changed, 663 insertions(+), 3 deletions(-)
Patrick McHardy (2):
[IPROUTE]: iplink: use netlink for link configuration
[IPROUTE]: VLAN support
next reply other threads:[~2007-06-13 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 17:02 Patrick McHardy [this message]
2007-06-13 17:02 ` [IPROUTE 01/02]: iplink: use netlink for link configuration Patrick McHardy
2007-06-13 17:02 ` [IPROUTE 02/02]: VLAN support Patrick McHardy
2007-06-13 17:48 ` [IPROUTE 00/02]: rtnl_link support Stephen Hemminger
2007-06-13 18:11 ` Patrick McHardy
2007-06-13 19:51 ` David Miller
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=20070613170229.8318.75488.sendpatchset@localhost.localdomain \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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).