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  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]
Date:	Tue, 27 Oct 2009 12:03:32 -0400
From:	Chris Mason <>
To:	Mel Gorman <>
Cc:	Frans Pop <>,
	David Rientjes <>,
	KOSAKI Motohiro <>,
	"Rafael J. Wysocki" <>,
	Linux Kernel Mailing List <>,
	Kernel Testers List <>,
	Pekka Enberg <>,
	Reinette Chatre <>,
	Bartlomiej Zolnierkiewicz <>,
	Karol Lewandowski <>,
	Mohamed Abbas <>,
	Jens Axboe <>,
	"John W. Linville" <>,
Subject: Re: [Bug #14141] order 2 page allocation failures in iwlagn

On Tue, Oct 27, 2009 at 03:52:24PM +0000, Mel Gorman wrote:
> > So, after the move to async/sync, a lot more pages are getting queued
> > for writeback - more than three times the number of pages are queued for
> > writeback with the vanilla kernel. This amount of congestion might be why
> > direct reclaimers and kswapd's timings have changed so much.
> > 
> Or more accurately, the vanilla kernel has queued up a lot more pages for
> IO than when the patch is reverted. I'm not seeing yet why this is.

[ sympathies over confusion about congestion...lots of variables here ]

If wb_kupdate has been able to queue more writes it is because the
congestion logic isn't stopping it.  We have congestion_wait(), but
before calling that in the writeback paths it says: are you congested?
and then backs off if the answer is yes.

Ideally, direct reclaim will never do writeback.  We want it to be able
to find clean pages that kupdate and friends have already processed.

Waiting for congestion is a funny thing, it only tells us the device has
managed to finish some IO or that a timeout has passed.  Neither event has
any relation to figuring out if the IO for reclaimable pages has

One option is to have the VM remember the hashed waitqueue for one of
the pages it direct reclaims and then wait on it.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists