All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, anton@samba.org, netdev@oss.sgi.com
Subject: Re: 100 network limit
Date: Thu, 28 Aug 2003 20:45:22 -0700	[thread overview]
Message-ID: <3F4ECC52.5000406@candelatech.com> (raw)
In-Reply-To: <20030828164143.536d8d8a.davem@redhat.com>

David S. Miller wrote:
> On Thu, 28 Aug 2003 14:46:39 -0700
> Ben Greear <greearb@candelatech.com> wrote:
> 
> 
>>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.)
> 
> 
> Right, it's also not going to fix the locking problems.
> 
> I would suggest two things:
> 
> 1) Ben's hashing patch for lookups.
> 
> 2) RCU'ing read access to the device list.
> 

I'm at least mostly on vacation for a week or so...  Here is a pointer
to the old patch I did..but it's ~2.5 years old.  If anyone wants
to get it working with recent code, please be my guest.

Otherwise, I'll try to get something together in a few weeks.

http://www.cs.helsinki.fi/linux/linux-kernel/2001-00/1227.html

Take it easy,
Ben

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

  reply	other threads:[~2003-08-29  3:45 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
2003-08-28 23:41     ` David S. Miller
2003-08-29  3:45       ` Ben Greear [this message]
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=3F4ECC52.5000406@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ak@suse.de \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --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 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.