lkml.org 
[lkml]   [2005]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] cpuset confine pdflush to its cpuset
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-10-24 08:46    [W:1.654 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site