All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: vlan@Scry.WANfear.com
Cc: "David S. Miller" <davem@redhat.com>,
	Dax Kelson <dkelson@gurulabs.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Holger Kiehl <Holger.Kiehl@dwd.de>,
	"vlan-devel (other)" <vlan-devel@lists.sourceforge.net>,
	Lennert <buytenh@gnu.org>, Gleb Natapov <gleb@nbase.co.il>
Subject: Re: [VLAN] Re: Should VLANs be devices or something else?
Date: Tue, 19 Jun 2001 18:24:22 -0700	[thread overview]
Message-ID: <3B2FFB46.BBA2BA2C@candelatech.com> (raw)
In-Reply-To: <3B2FCE0C.67715139@candelatech.com> <Pine.LNX.4.33.0106191641150.17061-100000@duely.gurulabs.com> <15151.55017.371775.585016@pizda.ninka.net> <3B2FDD62.EFC6AEB1@candelatech.com> <3B2FEEE0.C57EC336@sch.bme.hu>

Marcell Gal wrote:
> 

> I remember
> /proc/sys/net/ipv4/conf/
> was broken for about >300 devices. I do not know how's it today.

My VLAN code creates an entry for every vlan in /proc/net/vlan/
too, and it seems to quit creating entries after about 250 or so.
It's read-only info, so it doesn't seem to do too much harm.

I think there must be an 8-bit limit somewhere in the proc-fs.

> > Adding the hashed lookup for devices took the exponential curve out of
> > ip and ifconfig's performance, btw.
> 
> n^2 for creating n devices (in the unfortunate increasing or random
> order),
> (not 2^n), I guess.

It definately isn't fast, but then again, it is fast enough when you
only have 500 or so interfaces.  For the wierdos that want more, we
can just wait a little longer... :)

I'll offer the hashed-device-lookup
patch separately on my web site so it can be used if needed...

Ben

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2001-06-20  1:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19  8:19 VLAN in kernel? Holger Kiehl
2001-06-19 22:11 ` Should VLANs be devices or something else? Ben Greear
2001-06-19 22:45   ` Dax Kelson
2001-06-19 22:49     ` David S. Miller
2001-06-19 22:52       ` Dax Kelson
2001-06-19 23:16       ` Ben Greear
2001-06-20  0:31         ` Marcell Gal
2001-06-20  1:24           ` Ben Greear [this message]
2001-06-20  8:10         ` [VLAN] " Eran Man
2001-06-20  9:32       ` Gleb Natapov
2001-06-20  7:21   ` [VLAN] " Sander Steffann
2001-06-22  6:12     ` Peter C. Norton
2001-06-22  6:27       ` Albert D. Cahalan
2001-06-22  6:36         ` Ben Greear
2001-06-21 22:10   ` [Vlan-devel] " Guy Van Den Bergh
2001-06-21 22:54     ` Ben Greear
2001-06-22 15:00       ` Matthias Welwarsky
2001-06-22 15:46         ` Chris Wedgwood

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=3B2FFB46.BBA2BA2C@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Holger.Kiehl@dwd.de \
    --cc=buytenh@gnu.org \
    --cc=davem@redhat.com \
    --cc=dkelson@gurulabs.com \
    --cc=gleb@nbase.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vlan-devel@lists.sourceforge.net \
    --cc=vlan@Scry.WANfear.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.