Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932200AbWBTVUR (ORCPT ); Mon, 20 Feb 2006 16:20:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932341AbWBTVUQ (ORCPT ); Mon, 20 Feb 2006 16:20:16 -0500 Received: from e32.co.us.ibm.com ([32.97.110.150]:62377 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S932200AbWBTVUN (ORCPT ); Mon, 20 Feb 2006 16:20:13 -0500 Subject: [PATCH 0/3] map multiple blocks in get_block() and mpage_readpages() From: Badari Pulavarty To: christoph , mcao@us.ibm.com, akpm@osdl.org Cc: lkml , linux-fsdevel , pbadari@us.ibm.com Content-Type: text/plain Date: Mon, 20 Feb 2006 13:21:27 -0800 Message-Id: <1140470487.22756.12.camel@dyn9047017100.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1180 Lines: 39 Hi, Following patches add support to map multiple blocks in ->get_block(). This is will allow us to handle mapping of multiple disk blocks for mpage_readpages() and mpage_writepages() etc. Instead of adding new argument, I use "b_size" to indicate the amount of disk mapping needed for get_block(). And also, on success get_block() actually indicates the amount of disk mapping it did. Now that get_block() can handle multiple blocks, there is no need for ->get_blocks() which was added for DIO. [PATCH 1/3] pass b_size to ->get_block() [PATCH 2/3] map multiple blocks for mpage_readpages() [PATCH 3/3] remove ->get_blocks() support I noticed decent improvements (reduced sys time) on JFS, XFS and ext3. (on simple "dd" read tests). (rc3.mm1) (rc3.mm1 + patches) real 0m18.814s 0m18.482s user 0m0.000s 0m0.004s sys 0m3.240s 0m2.912s Andrew, Could you include it in -mm tree ? Comments ? Thanks, Badari - 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/