From: jamal <hadi@cyberus.ca>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vlad Dogaru <ddvlad@rosedu.org>,
Octavian Purdila <opurdila@ixiacom.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/3] net: add device groups
Date: Mon, 10 Jan 2011 09:24:10 -0500 [thread overview]
Message-ID: <1294669450.6063.319.camel@mojatatu> (raw)
In-Reply-To: <1294668505.3583.9.camel@jlt3.sipsolutions.net>
On Mon, 2011-01-10 at 15:08 +0100, Johannes Berg wrote:
>
> Right, but where would you want to use it -- what's the use case right
> now? Your ppp example here makes me think the use case is some PPP
> endpoint server that has lots of these interfaces.
That was just an example because someone mentioned PPP earlier.
Originally, this came from someone (Octavian?) trying to setup
a gazillion netdevs for testing purposes and then needing to
do "ip link ls dummy*" which causes a gazillion messages between
kernel and user space and all the filtering of what dummy* being
done in user space.
> It also means the
> grouping is entirely user-space controlled. In this case, the idea of
> automatically grouping based on the device structure seems pointless.
You still havent said what you want this grouping for. What is your
use case? ;->
cheers,
jamal
next prev parent reply other threads:[~2011-01-10 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 11:38 [PATCH 0/3] net: add device groups Vlad Dogaru
2011-01-10 11:38 ` [PATCH 1/3] net_device: add support for network " Vlad Dogaru
2011-01-10 11:38 ` [PATCH 2/3] net/dummy: add device group parameter Vlad Dogaru
2011-01-10 21:37 ` David Miller
2011-01-11 12:17 ` Vlad Dogaru
2011-01-10 11:38 ` [PATCH 3/3] netlink: support setting devgroup parameters Vlad Dogaru
2011-01-10 13:14 ` jamal
2011-01-11 12:13 ` Vlad Dogaru
2011-01-11 12:40 ` jamal
2011-01-10 13:41 ` [PATCH 0/3] net: add device groups Johannes Berg
2011-01-10 14:00 ` jamal
2011-01-10 14:08 ` Johannes Berg
2011-01-10 14:24 ` jamal [this message]
2011-01-10 14:38 ` Johannes Berg
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=1294669450.6063.319.camel@mojatatu \
--to=hadi@cyberus.ca \
--cc=ddvlad@rosedu.org \
--cc=johannes@sipsolutions.net \
--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