From: Stephen Hemminger <stephen@networkplumber•org>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Jamal Hadi Salim <jhs@mojatatu•com>,
vyasevic@redhat•com, Stephen Hemminger <shemminger@vyatta•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [RFC] bridge and friends: reduce TheLinuxWay(tm)
Date: Wed, 16 Oct 2013 11:49:34 -0700 [thread overview]
Message-ID: <20131016114934.2265dbe5@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1381948550.2045.136.camel@edumazet-glaptop.roam.corp.google.com>
On Wed, 16 Oct 2013 11:35:50 -0700
Eric Dumazet <eric.dumazet@gmail•com> wrote:
> On Wed, 2013-10-16 at 13:49 -0400, Jamal Hadi Salim wrote:
>
> > I think we need some filtering in the kernel. As it stands today,
> > unfortunately you get everything ;-> I was suprised at the amount of
> > data i get from the kernel these days when i ask for a simple netdev
> > info (I think no less than 1K per netdev; everything from /proc entries
> > from some bread crumbs i dont see any use for.
>
> By the way, "ip link show dev xxxx" seems to dump all devices info from
> the kernel...
>
>
As I remember.
The problem is that according to original netlink design there is supposed to
be a NLM_F_MATCH, but it seems it never got implemented right, and the legacy
of breaking applications keeps it from happening.
next prev parent reply other threads:[~2013-10-16 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 21:32 [RFC] bridge and friends: reduce TheLinuxWay(tm) Jamal Hadi Salim
2013-10-14 21:41 ` Stephen Hemminger
2013-10-16 13:54 ` Jamal Hadi Salim
2013-10-16 14:05 ` Jamal Hadi Salim
2013-10-16 17:11 ` Vlad Yasevich
2013-10-16 17:49 ` Jamal Hadi Salim
2013-10-16 18:35 ` Eric Dumazet
2013-10-16 18:49 ` Stephen Hemminger [this message]
2013-10-16 18:50 ` Vlad Yasevich
2013-10-16 19:02 ` Jamal Hadi Salim
2013-10-16 20:19 ` Jamal Hadi Salim
2013-10-16 20:22 ` Vlad Yasevich
2013-10-18 10:42 ` Jamal Hadi Salim
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=20131016114934.2265dbe5@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber$(echo .)org \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
--cc=vyasevic@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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