From: Andrew Morton <akpm@linux-foundation.org>
To: Peter W Morreale <pmorreale@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Add /proc controls for pdflush threads
Date: Wed, 31 Dec 2008 00:01:48 -0800 [thread overview]
Message-ID: <20081231000148.6a2f8e3f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081230231233.10427.11443.stgit@hermosa.site>
On Tue, 30 Dec 2008 16:12:33 -0700 Peter W Morreale <pmorreale@novell.com> wrote:
> From: \"Peter W. Morreale\" <pmorreale@novell.com>
>
> This patch adds /proc entries to give the admin the ability to
> control the minimum and maximum number of pdflush threads. This allows
> finer control of pdflush on both large and small machines.
>
> The patch adds '/proc/sys/vm/nr_pdflush_threads_min' and
> '/proc/sys/vm/nr_pdflush_threads_max' with r/w permissions.
Why is this needed? Where's the benefit? What observations led you to
develop this patch? etc.
> --- a/include/linux/sysctl.h
> +++ b/include/linux/sysctl.h
> @@ -205,6 +205,8 @@ enum
> VM_PANIC_ON_OOM=33, /* panic at out-of-memory */
> VM_VDSO_ENABLED=34, /* map VDSO into new processes? */
> VM_MIN_SLAB=35, /* Percent pages ignored by zone reclaim */
> + VM_NR_PDFLUSH_THREADS_MAX=36, /* nr_pdflush_threads_max */
> + VM_NR_PDFLUSH_THREADS_MIN=37, /* nr_pdflush_threads_min */
> };
We don't do this any more...
> .proc_handler = &proc_dointvec,
> },
> {
> + .ctl_name = VM_NR_PDFLUSH_THREADS_MIN,
please just use CTL_UNNUMBERED here.
next prev parent reply other threads:[~2008-12-31 8:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 23:12 [PATCH 0/2] pdflush fix and enhancement Peter W Morreale
2008-12-30 23:12 ` [PATCH 1/2] Fix pdflush thread creation upper bound Peter W Morreale
2008-12-30 23:12 ` [PATCH 2/2] Add /proc controls for pdflush threads Peter W Morreale
2008-12-30 23:59 ` Randy Dunlap
2008-12-31 0:15 ` Peter W. Morreale
2008-12-31 2:38 ` Peter W. Morreale
2008-12-31 3:30 ` Randy Dunlap
2008-12-31 8:01 ` Andrew Morton [this message]
2008-12-31 14:54 ` Peter W. Morreale
2008-12-31 0:28 ` [PATCH 0/2] pdflush fix and enhancement Andi Kleen
2008-12-31 1:56 ` Peter W. Morreale
2008-12-31 2:46 ` Andi Kleen
2008-12-31 4:11 ` Peter W. Morreale
2008-12-31 7:08 ` Dave Chinner
2008-12-31 15:40 ` Peter W. Morreale
2009-01-01 23:27 ` Dave Chinner
2009-01-02 2:07 ` Peter W. Morreale
2008-12-31 13:27 ` Andi Kleen
2008-12-31 16:08 ` Peter W. Morreale
2009-01-01 1:48 ` Andi Kleen
2008-12-31 11:40 ` Martin Knoblauch
-- strict thread matches above, loose matches on Subject: below --
2008-12-31 19:10 [PATCH 0/2] fix pdflush races and enhancement v2 Peter W Morreale
2008-12-31 19:10 ` [PATCH 2/2] Add /proc controls for pdflush threads Peter W Morreale
2008-12-31 21:35 ` Rik van Riel
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=20081231000148.6a2f8e3f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmorreale@novell.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