From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with SMTP id p3BIXXo3105899 for ; Mon, 11 Apr 2011 13:33:33 -0500 Received: from bombadil.infradead.org (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id E4EF21E0B619 for ; Mon, 11 Apr 2011 11:36:53 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) by cuda.sgi.com with ESMTP id 2T0orq1EMurujJHz for ; Mon, 11 Apr 2011 11:36:53 -0700 (PDT) Date: Mon, 11 Apr 2011 14:36:53 -0400 From: Christoph Hellwig Subject: Re: [PATCH 2/2] xfs: kick inode writeback when low on memory 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-Disposition: inline In-Reply-To: <1302157196-1988-3-git-send-email-david@fromorbit.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com 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 _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs