netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: vyasevic@redhat.com, Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	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 15:02:04 -0400	[thread overview]
Message-ID: <525EE2AC.50002@mojatatu.com> (raw)
In-Reply-To: <525EE00A.20209@redhat.com>

On 10/16/13 14:50, Vlad Yasevich wrote:

> Right.  ip link show is dumb.  It asks for info from all devices and
> then filters based on the device you asked for, but the filtering
> is done in iproute instead of the kernel.
>

That maybe small flaw in iproute2 - but there's no issue in the kernel.
You can send an ifi and specify the proper ifindex of choice.
But you cant do the same with bridge.
Thats what i was whining to Stephen about. I get every
bridge port with no exception and there's no way to specify one
(the ifi ifindex is never used).
Think 20K bridge ports - each giving me 1K of data ...
scalability problem

cheers,
jamal

  reply	other threads:[~2013-10-16 19:09 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
2013-10-16 18:50           ` Vlad Yasevich
2013-10-16 19:02             ` Jamal Hadi Salim [this message]
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=525EE2AC.50002@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=stephen@networkplumber.org \
    --cc=vyasevic@redhat.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;
as well as URLs for NNTP newsgroup(s).