linux-kernel - Re: [RFC][PATCH] try not to let dirty inodes fester

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] [day] [month] [year] [list]

Message-ID: <1286834490.20322.8.camel@nimitz>
Date:	Mon, 11 Oct 2010 15:01:30 -0700
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Dave Chinner <david@...morbit.com>, linux-kernel@...r.kernel.org,
	hch@...radead.org, lnxninja@...ux.vnet.ibm.com, axboe@...nel.dk,
	pbadari@...ibm.com, Yuri L Volobuev <volobuev@...ibm.com>
Subject: Re: [RFC][PATCH] try not to let dirty inodes fester

Dave, Christoph,

Thanks again for looking at this.  It turned out not to be dirty data at
all that was causing this.  It was dispose_list() taking extraordinarily
long to complete.  There were cases where it was taking 2 or 3 minutes
per batch of ~75 inodes.  This was all due to the underlying filesystem
(GPFS) taking a couple of seconds for each clear_inode().  This kept the
kernel from being able to do any slab reclaim effectively.

Sorry for the noise.

-- Dave

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