From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
torvalds@osdl.org, fabbione@ubuntu.com
Subject: Re: VFS nr_files accounting
Date: Tue, 7 Mar 2006 17:39:16 +0530 [thread overview]
Message-ID: <20060307120916.GD5946@in.ibm.com> (raw)
In-Reply-To: <20060306230639.24eacb6c.akpm@osdl.org>
On Mon, Mar 06, 2006 at 11:06:39PM -0800, Andrew Morton wrote:
> Dipankar Sarma <dipankar@in.ibm.com> wrote:
> >
> > > I think we should seriously consider these patches for 2.6.16
> >
> > Isn't it a little too late in the 2.6.16 cycle ? I would have
> > liked a little more time in -mm. Anyway, it is Linus' call.
> > I can refresh the patches and submit against latest mainline
> > if Linus and Andrew want.
>
> I'd view a 2.6.16 merge as relatively low-risk. My main concern would be
> possible breakage of those whacky route-cache workloads.
Yes, I was hoping that more time in -mm would bring out those
whacky corner case OOM/latency problems.
Anyway, here is the kernel paramenter documentation patch.
I am not sure if I got the restrictions in square bracket
right.
Thanks
Dipankar
Update kernel paramenters documentation for new RCU tuning
paramenters.
Signed-off-by: Dipankar Sarma <dipankar@in.ibm.com>
---
Documentation/kernel-parameters.txt | 13 +++++++++++++
1 files changed, 13 insertions(+)
diff -puN Documentation/kernel-parameters.txt~rcu-tuning-parm-doc Documentation/kernel-parameters.txt
--- linux-2.6.16-rc3-rcu/Documentation/kernel-parameters.txt~rcu-tuning-parm-doc 2006-03-07 17:23:52.000000000 +0530
+++ linux-2.6.16-rc3-rcu-dipankar/Documentation/kernel-parameters.txt 2006-03-07 17:33:59.000000000 +0530
@@ -1280,6 +1280,19 @@ running once the system is up.
New name for the ramdisk parameter.
See Documentation/ramdisk.txt.
+ rcu.blimit= [KNL,BOOT] Set maximum number of finished
+ RCU callbacks to process in one batch.
+
+ rcu.qhimark= [KNL,BOOT] Set threshold of queued
+ RCU callbacks over which batch limiting is disabled.
+
+ rcu.qlowmark= [KNL,BOOT] Set threshold of queued
+ RCU callbacks below which batch limiting is re-enabled.
+
+ rcu.rsinterval= [KNL,BOOT,SMP] Set the number of additional
+ RCU callbacks to queued before forcing reschedule
+ on all cpus.
+
rdinit= [KNL]
Format: <full_path>
Run specified binary instead of /init from the ramdisk,
_
prev parent reply other threads:[~2006-03-07 12:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 10:25 VFS nr_files accounting David S. Miller
2006-03-04 14:17 ` Dipankar Sarma
2006-03-04 22:22 ` David S. Miller
2006-03-04 22:28 ` David S. Miller
2006-03-04 22:32 ` David S. Miller
2006-03-05 7:05 ` Dipankar Sarma
2006-03-05 7:37 ` David S. Miller
2006-03-05 11:38 ` Dipankar Sarma
2006-03-06 20:39 ` David S. Miller
2006-03-07 6:41 ` Dipankar Sarma
2006-03-07 6:47 ` David S. Miller
2006-03-07 8:02 ` Dipankar Sarma
2006-03-07 6:53 ` Nick Piggin
2006-03-07 7:00 ` David S. Miller
2006-03-07 8:09 ` Dipankar Sarma
2006-03-07 8:55 ` Fabio Massimo Di Nitto
2006-03-07 7:06 ` Andrew Morton
2006-03-07 12:09 ` Dipankar Sarma [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=20060307120916.GD5946@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=fabbione@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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