Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753569Ab0BYIUi (ORCPT ); Thu, 25 Feb 2010 03:20:38 -0500 Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:41029 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753258Ab0BYIUg (ORCPT ); Thu, 25 Feb 2010 03:20:36 -0500 Date: Thu, 25 Feb 2010 09:20:35 +0100 From: Jens Axboe To: Alan Stern Cc: linux-pm , linux-kernel Subject: Re: Testing for dirty buffers on a block device Message-ID: <20100225082035.GR1025@kernel.dk> References: <20100224190942.GG1025@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1218 Lines: 31 On Wed, Feb 24 2010, Alan Stern wrote: > On Wed, 24 Feb 2010, Jens Axboe wrote: > > > > > But if you wanted, I guess the only way would be to lookup > > > > dirty/writeback pages on the bdev inode mapping. For that you'd need the > > > > bdev, not the gendisk or the queue though. > > > > > > I can get the bdev from the gendisk by calling bdget_disk() with a > > > partition number of 0, right? What would the next step be? Would this > > > check for dirty pages associated with any of the partitions or would it > > > only look at pages associated with the inode for the entire disk? > > > > It would cover the entire bdev. > > Okay, so once I've got the bdev, how do I look up the dirty/writeback > pages on the inode mapping? I _think_ you can get away with not doing a radix lookup for dirty pages, just looking at the BDI_RECLAIMABLE stat on the bdi. That would be: bdi_stat(bdev->bd_inode->i_mapping->backing_dev_info, BDI_RECLAIMABLE); -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/