From: Vlad Dogaru <ddvlad@rosedu.org>
To: hadi@cyberus.ca
Cc: Octavian Purdila <opurdila@ixiacom.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Stephen Hemminger <shemminger@vyatta.com>,
netdev@vger.kernel.org,
Lucian Adrian Grijincu <lucian.grijincu@gmail.com>
Subject: Re: [PATCH] iproute2: ip: add wilcard support for device matching
Date: Sun, 19 Dec 2010 09:32:17 +0000 (UTC)
Date: Mon, 20 Dec 2010 11:23:18 -0800 [thread overview]
Message-ID: <4D0FAD26.8050908@rosedu.org> (raw)
In-Reply-To: <1292593088.2668.43.camel@mojatatu>
On 12/17/2010 5:38 AM, jamal wrote:
> On Fri, 2010-12-10 at 20:06 +0200, Octavian Purdila wrote:
>
>>> $ ip link add link bond0 "vlan\*199" type vlan id 199
>>> $ ifconfig "vlan\*199"
>>
>> :) Then use a special dev keyword like dev* ?
>>
>> $ ip link set dev* dummy set
>>
>> Or use a new flag to allow expansion?
>>
>> $ ip -e link set dev dummy* set
>
> There was something ive always wanted to do but
> havent had time. It will cut time in a big way the
> user-kernel interaction in precisely your situation.
>
> Add a new general purpose netdev 32 bit tag. You can use this
> feature to "group" netdevs. The group "all netdevs" is 0 - which
> is the default.
> I can group individual dummy interfaces into group 1.
> ip link dev dummy0 set group 1
> ..
> ..
> ip link dev dummy99 set group 1
>
> Then i can send a query to only ifup and ignore
> the 1000 vlans that exist.
>
> ip link dev ls group 1
>
> or if i didnt list the group, then group 0 is assumed.
I'll try to implement this approach in the next few days.
Vlad
next prev parent reply other threads:[~2010-12-19 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:58 [PATCH] iproute2: ip: add wilcard support for device matching Octavian Purdila
2010-12-10 16:18 ` Stephen Hemminger
2010-12-10 16:32 ` Eric Dumazet
2010-12-10 17:32 ` Octavian Purdila
2010-12-10 17:42 ` Eric Dumazet
2010-12-10 18:06 ` Octavian Purdila
2010-12-17 13:38 ` jamal
2010-12-19 9:32 ` Vlad Dogaru [this message]
2010-12-21 13:14 ` jamal
2011-01-08 21:10 ` Philip Prindeville
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=4D0FAD26.8050908@rosedu.org \
--to=ddvlad@rosedu.org \
--cc=eric.dumazet@gmail.com \
--cc=hadi@cyberus.ca \
--cc=lucian.grijincu@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.