linux-kernel - Re: [PATCH 03/10] writeback: stop background writeback when below background threshold

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1253809560.18939.69.camel@laptop>
Date:	Thu, 24 Sep 2009 18:26:00 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-kernel@...r.kernel.org, fengguang.wu@...el.com,
	shaohua.li@...el.com, chris.mason@...cle.com, jack@...e.cz
Subject: Re: [PATCH 03/10] writeback: stop background writeback when below
 background threshold

On Thu, 2009-09-24 at 18:13 +0200, Jens Axboe wrote:

> > > >  	for (;;) {
> > > >  		/*
> > > > +		 * Stop writeback when nr_pages has been consumed
> > > >  		 */
> > > > +		if (args->nr_pages <= 0)
> > > >  			break;
> > > >  
> > > >  		/*
> > > > +		 * For background writeout, stop when we are below the
> > > > +		 * background dirty threshold
> > > >  		 */
> > > > +		if (args->for_background && !over_bground_thresh())
> > > >  			break;
> > > 
> > > 
> > > What I'm not getting is why this is conditional on for_background(),
> > > shouldn't we always stop writeback when below the background threshold?
> > 
> > Ah, that would be for things like sync, which need to write out
> > everything, right?
> 
> Yes, wb_writeback() handles any kind of writeback. The definition of our
> background writeout is to stop when we are no longer over the background
> writeout threshold.

Right, ok

Acked-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>

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