linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: taka@valinux.co.jp, Simon.Derr@bull.net,
	linux-kernel@vger.kernel.org, clameter@sgi.com,
	torvalds@osdl.org, linux-mm@kvack.org
Subject: Re: [PATCH] cpuset confine pdflush to its cpuset
Date: Sun, 23 Oct 2005 23:40:32 -0700	[thread overview]
Message-ID: <20051023234032.5e926336.akpm@osdl.org> (raw)
In-Reply-To: <20051023233237.0982b54b.pj@sgi.com>

Paul Jackson <pj@sgi.com> wrote:
>
> Takahashi-san wrote:
> > I realized CPUSETS has another problem around pdflush.
> 
> Excellent observation.  I had not realized this.
> 
> Thank-you for pointing it out.
> 
> I don't have plans.  Do you have any suggestions?

Per-zone dirty thresholds (quite messy), per-zone writeback (horrific,
linear searches or data structure proliferation everywhere).

Let's see a (serious) worload/testcase first, hey?  vmscan.c writeback off
the LRU is a bit slow, but we should be able to make it suffice.

>   ( Anyone know what the "pd" stands for in pdflush ?? )

"page dirty"?  It's what bdflush became when writeback went from
being block-based to being page-based.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-24  6:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051024001913.7030.71597.sendpatchset@jackhammer.engr.sgi.com>
2005-10-24  5:52 ` Hirokazu Takahashi
2005-10-24  6:32   ` Paul Jackson
2005-10-24  6:40     ` Andrew Morton [this message]
2005-10-24  6:49       ` Paul Jackson
2005-10-24  7:13         ` Hirokazu Takahashi
2005-10-24  7:37           ` Paul Jackson

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=20051023234032.5e926336.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Simon.Derr@bull.net \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    --cc=taka@valinux.co.jp \
    --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