All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@wildopensource.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Number of proc entries based on NR_CPUS ?
Date: Sat, 08 Nov 2003 18:35:59 -0500	[thread overview]
Message-ID: <1068334559.2039.11.camel@socrates> (raw)
In-Reply-To: <20031108190310.GG3440@krispykreme>

On Sat, 2003-11-08 at 14:03, Anton Blanchard wrote:
> Hi Martin,
> 
> > Here is a patch that makes the number of /proc entries be based on
> > NR_CPUS instead of just having a fixed number.  I think it is a good
> > idea now that big Linux machines are starting to appear.
> > 
> > The proper constant and slope of increase are up for argument too.
> > 
> > Patch is against the latest linux-2.5 bk tree.
> 
> I think I first bumped that to 16k, that was needed on a 32way box.
> At 128way my gut feeling is its 32k.
> 

Okay, those are useful numbers to have.  This seems to be higher than
what is required by SGI's sn2.

> Linking the number of proc entries to the number of cpus is a bit crude
> but its better than having it fixed.

Yeah, I'm not sure what a really good solution is.  I really don't have
an urge to tear apart the proc code to make it more dynamic than this
compile time option.

> 
> FYI I think some networking people were complaining about this limit
> when they create gobs of network interfaces (dummy devices?  ipsec?).
> Each interface creates a bunch of /proc/sys/net entries...

Based on your guidlines above, we need a number of proc entries more
like:

8192 + 256*NR_CPUS

mh

-- 
Martin Hicks                Wild Open Source Inc.
mort@wildopensource.com     613-266-2296



      reply	other threads:[~2003-11-08 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 17:42 [PATCH 2.6] Number of proc entries based on NR_CPUS ? Martin Hicks
2003-11-08 19:03 ` Anton Blanchard
2003-11-08 23:35   ` Martin Hicks [this message]

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=1068334559.2039.11.camel@socrates \
    --to=mort@wildopensource.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.