All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: panther@balabit.hu
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Resend: [IPROUTE2 PATCH] Interface group as new ip link option
Date: Tue, 16 Oct 2007 08:08:47 -0400	[thread overview]
Message-ID: <1192536528.4480.65.camel@localhost> (raw)
In-Reply-To: <4714A4C3.10103@balabit.hu>

On Tue, 2007-16-10 at 13:47 +0200, Laszlo Attila Toth wrote:

> Hm, the main problem (for me) is that it requires more then one value 
> per net device and it should be limited. But if I say it is 5 for 
> instance, anyone can say it is not enough for him.

Yes, those pesky humans, you give them an inch and they want a mile ;->
I think 32 for example is better than 1. So if you use a u32 variable
doesnt pollute the netdevice that much - and used as a bitmap, then
setting any of the 32 bits implies the device is in that group. This of
course limits the group ids to be (1..32). Your mileage may vary.

> ip link set ppp0 group 10
> also if "ip link set..." works for multiple interfaces it is already 
> done. If it is not, it will affect positively all other settings :)

nice.
The part that is not very useful today with ifconfig or ip link ls is i
have only two choices: Either i ask for all devices or for one; i cant
ask for something in the middle. If i can group them together then i can
solve that problem sith some user space plumbing (which avoids 10K
netlink messages). 
"get ppp*" may actually be a totally separate call which also traverses
the list in the kernel and just returns the matching devices. 

cheers,
jamal


      reply	other threads:[~2007-10-16 12:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  8:01 [PATCH 0/2] Interface groups Laszlo Attila Toth
2007-10-16  8:01 ` Laszlo Attila Toth
2007-10-16  8:50   ` Philip Craig
2007-10-16  9:47     ` Laszlo Attila Toth
2007-10-16  8:01 ` [PATCH 1/2] Interface group: core (netlink) part Laszlo Attila Toth
2007-10-16  8:01   ` Laszlo Attila Toth
2007-10-16  8:34     ` Patrick McHardy
2007-10-16  8:01   ` [PATCH 2/2] Interface group match - netfilter part Laszlo Attila Toth
2007-10-16  8:01     ` Laszlo Attila Toth
2007-10-16  8:30       ` Patrick McHardy
2007-10-16  9:46         ` Laszlo Attila Toth
2007-10-16 14:46         ` Jan Engelhardt
2007-10-17  9:08         ` Laszlo Attila Toth
2007-10-17  9:11           ` Patrick McHardy
2007-10-16  8:01 ` [IPROUTE2 PATCH] Interface group as new ip link option Laszlo Attila Toth
2007-10-16  8:01   ` Laszlo Attila Toth
2007-10-16  8:38     ` Patrick McHardy
2007-10-16  9:33       ` Laszlo Attila Toth
2007-10-16  9:03   ` Resend: " Laszlo Attila Toth
2007-10-16  9:11     ` Patrick McHardy
2007-10-16 10:45   ` jamal
2007-10-16 11:05     ` Laszlo Attila Toth
2007-10-16 11:26       ` jamal
2007-10-16 11:47         ` Laszlo Attila Toth
2007-10-16 12:08           ` jamal [this message]

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=1192536528.4480.65.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=panther@balabit.hu \
    /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.