mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Hicks <mort@wildopensource.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6] Number of proc entries based on NR_CPUS ?
Date: Sat, 08 Nov 2003 12:42:58 -0500	[thread overview]
Message-ID: <1068313378.685.7.camel@socrates> (raw)


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.

Opinions?
mh

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


# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1359  -> 1.1360 
#	include/linux/proc_fs.h	1.27    -> 1.28   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/11/08	mort@green.i.bork.org	1.1360
# Make PROC_NDYNAMIC based on NR_CPUS.
# --------------------------------------------
#
diff -Nru a/include/linux/proc_fs.h b/include/linux/proc_fs.h
--- a/include/linux/proc_fs.h	Sat Nov  8 12:38:34 2003
+++ b/include/linux/proc_fs.h	Sat Nov  8 12:38:34 2003
@@ -27,7 +27,7 @@
 /* Finally, the dynamically allocatable proc entries are reserved: */
 
 #define PROC_DYNAMIC_FIRST 4096
-#define PROC_NDYNAMIC      16384
+#define PROC_NDYNAMIC      (4096+32*NR_CPUS)
 
 #define PROC_SUPER_MAGIC 0x9fa0
 



             reply	other threads:[~2003-11-08 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 17:42 Martin Hicks [this message]
2003-11-08 19:03 ` Anton Blanchard
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=1068313378.685.7.camel@socrates \
    --to=mort@wildopensource.com \
    --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 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®