From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/2] xfs: kick inode writeback when low on memory
Date: Mon, 11 Apr 2011 14:36:53 -0400
Message-ID: <20110411183653.GD32346@infradead.org>
References: <1302157196-1988-1-git-send-email-david@fromorbit.com>
 <1302157196-1988-3-git-send-email-david@fromorbit.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
To: Dave Chinner <david@fromorbit.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([18.85.46.34]:59574 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755260Ab1DKSgy (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 11 Apr 2011 14:36:54 -0400
Content-Disposition: inline
In-Reply-To: <1302157196-1988-3-git-send-email-david@fromorbit.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

How do you produce so many atime-dirty inodes?  With relatime we
should have cut down on the requirement for those a lot.

Do you have traces that show if we're kicking off additional data
writeback this way too, or just pushing timestamp updates into
the AIL?

Either way the actual patch looks good,


Reviewed-by: Christoph Hellwig <hch@lst.de>