From: Anton Blanchard <anton@samba.org>
To: Martin Hicks <mort@wildopensource.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] Number of proc entries based on NR_CPUS ?
Date: Sun, 9 Nov 2003 06:03:10 +1100 [thread overview]
Message-ID: <20031108190310.GG3440@krispykreme> (raw)
In-Reply-To: <1068313378.685.7.camel@socrates>
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.
Linking the number of proc entries to the number of cpus is a bit crude
but its better than having it fixed.
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...
Anton
next prev parent reply other threads:[~2003-11-08 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 17:42 Martin Hicks
2003-11-08 19:03 ` Anton Blanchard [this message]
2003-11-08 23:35 ` Martin Hicks
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=20031108190310.GG3440@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@wildopensource.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
all inboxes | Powered by JetHome®