mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: pdflush question...
Date: Wed, 03 Sep 2003 13:12:51 -0400	[thread overview]
Message-ID: <1062609171.7000.3.camel@boobies.awol.org> (raw)
In-Reply-To: <14227.1062581053@www37.gmx.net>

On Wed, 2003-09-03 at 05:24, Daniel Blueman wrote:
> Is it worth having a kernel config option to vary the number of 'pdflush'
> kernel threads?

I suspect no.

> For embedded, systems with no swap and maybe uniproc (?), perhaps one
> pdflush kthread would do?

Yes.  Definitely.  In fact, I think that, for all systems, the initial
default should perhaps be one.

But note that the reason for n>1 pdflush threads is neither swap or
processor related.  The multiple threads can keep multiple block devices
busy, since one thread blocking on I/O will not affect another one.

I guess the real test would be to set MIN_PDFLUSH_THREADS to one and see
if one is enough for the average machines.  If the number quickly jumps
to 2 or more... then we know its a bad idea.

> 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?

Number of spindles, yes.  But how do we know that?  And its just the
number of busy spindles, really.

I say we drop down to one.

	Robert Love



      parent reply	other threads:[~2003-09-03 17:02 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
2003-09-03 17:12 ` Robert Love [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=1062609171.7000.3.camel@boobies.awol.org \
    --to=rml@tech9.net \
    --cc=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®