linux-kernel - Re: regression in page writeback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1253608335.8439.283.camel@twins>
Date:	Tue, 22 Sep 2009 10:32:14 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	"Li, Shaohua" <shaohua.li@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"richard@....demon.co.uk" <richard@....demon.co.uk>,
	"jens.axboe@...cle.com" <jens.axboe@...cle.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	Chris Mason <chris.mason@...cle.com>
Subject: Re: regression in page writeback

On Tue, 2009-09-22 at 16:24 +0800, Wu Fengguang wrote:
> On Tue, Sep 22, 2009 at 04:09:25PM +0800, Peter Zijlstra wrote:
> > On Tue, 2009-09-22 at 16:05 +0800, Wu Fengguang wrote:
> > > 
> > > I'm not sure how this patch stopped the "overshooting" behavior.
> > > Maybe it managed to not start the background pdflush, or the started
> > > pdflush thread exited because it found writeback is in progress by
> > > someone else?
> > > 
> > > -               if (bdi_nr_reclaimable) {
> > > +               if (bdi_nr_reclaimable > bdi_thresh) {
> > 
> > The idea is that we shouldn't move more pages from dirty -> writeback
> > when there's not actually that much dirty left.
> 
> IMHO this makes little sense given that pdflush will move all dirty
> pages anyway. pdflush should already be started to do background
> writeback before the process is throttled, and it is designed to sync
> all current dirty pages as quick as possible and as much as possible.

Not so, pdflush (or now the bdi writer thread thingies) should not
deplete all dirty pages but should stop writing once they are below the
background limit.

> > Now, I'm not sure about the > bdi_thresh part, I've suggested to maybe
> > use bdi_thresh/2 a few times, but it generally didn't seem to make much
> > of a difference.
> 
> One possible difference is, the process may end up waiting longer time
> in order to sync write_chunk pages and quit the throttle. This could
> hurt the responsiveness of the throttled process.

Well, that's all because this congestion_wait stuff is borken..

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/