From: Andrew Morton <akpm@osdl.org>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pdflush question...
Date: Wed, 3 Sep 2003 08:38:40 -0700 [thread overview]
Message-ID: <20030903083840.768cfd58.akpm@osdl.org> (raw)
In-Reply-To: <14227.1062581053@www37.gmx.net>
Daniel Blueman <daniel.blueman@gmx.net> wrote:
>
> Is it worth having a kernel config option to vary the number of 'pdflush'
> kernel threads?
>
> For embedded, systems with no swap and maybe uniproc (?), perhaps one
> pdflush kthread would do?
Probably it should just be set to one by default anyway. One pdflush is
good at serving lots of spindles.
> Perhaps more generally, the number could be linked to the number of
> processors and/or swap devices or spindles- this would eliminate having to configure
> it, and improve downward and upward scaling, perhaps?
Well the kernel will create up to eight pdflush instances according to the
current load. That kinda works.
next prev parent reply other threads:[~2003-09-03 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 9:24 Daniel Blueman
2003-09-03 15:38 ` Andrew Morton [this message]
2003-09-03 17:12 ` Robert Love
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=20030903083840.768cfd58.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=daniel.blueman@gmx.net \
--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®