netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Andi Kleen <ak@suse.de>
Cc: Anton Blanchard <anton@samba.org>, netdev@oss.sgi.com
Subject: Re: 100 network limit
Date: Thu, 28 Aug 2003 14:46:39 -0700	[thread overview]
Message-ID: <3F4E783F.6080707@candelatech.com> (raw)
In-Reply-To: <20030828210855.58759b69.ak@suse.de>

Andi Kleen wrote:
> On Fri, 29 Aug 2003 04:00:19 +1000
> Anton Blanchard <anton@samba.org> wrote:
> 
> 
> 
>>Anyway as a short term fix Jamal suggested making a sysctl for this
>>maximum. If fixing this all properly is out of the question for 2.6,
>>would the sysctl approach be satisfactory? The other option is to just
>>bump the limit and recognise that the user is on his own if performance
>>sucks.
> 
> 
> You could just add a bitmap with a reasonable upper limit (1024?) and use 
> find_first_zero_bit()  I doubt doing that would be very intrusive.
> 
> -Andi

Since you can rename devices, that might not work.  A long time ago I
hashed the devices, both by name and by index...that gives good lookup performance, at least.  As for
create-time issues, that is definately slow path, and even searching linearly
4 or 8k devices is not a big deal (in my opinion).  So, why not make the hard-coded
100 limit be more like 8196 or something really large?  (It could still be adjustable
if needed.)

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2003-08-28 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 18:00 100 network limit Anton Blanchard
2003-08-28 19:08 ` Andi Kleen
2003-08-28 21:46   ` Ben Greear [this message]
2003-08-28 23:41     ` David S. Miller
2003-08-29  3:45       ` Ben Greear
2003-08-29  0:03     ` Andi Kleen

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=3F4E783F.6080707@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ak@suse.de \
    --cc=anton@samba.org \
    --cc=netdev@oss.sgi.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).