Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965125AbVL2JNO (ORCPT ); Thu, 29 Dec 2005 04:13:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965124AbVL2JNN (ORCPT ); Thu, 29 Dec 2005 04:13:13 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1]:9608 "EHLO mail.cs.helsinki.fi") by vger.kernel.org with ESMTP id S965123AbVL2JNN (ORCPT ); Thu, 29 Dec 2005 04:13:13 -0500 Date: Thu, 29 Dec 2005 11:12:57 +0200 (EET) From: Pekka J Enberg To: cai cc: OGAWA Hirofumi , linux-kernel Subject: Re: [RFC][fat] use mpage_readpage when cluster size is page-alignment In-Reply-To: <43B3A3D8.6050605@gmail.com> Message-ID: References: <87u0ctwf93.fsf@devron.myhome.or.jp> <43B3844A.5050401@gmail.com> <84144f020512290006x71d2c245s5e148fae15720d59@mail.gmail.com> <43B3A3D8.6050605@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1018 Lines: 23 On Thu, 29 Dec 2005, cai wrote: > > I am not sure I am following you. Shouldn't do_mpage_readpage work for > > all adjacent blocks regardless of whether block size is page-aligned > > or not? What's is the performance problem you're thinking of? > > no, not block size but cluster size > as you know, in FAT, file is organized in clusters > and one cluster could have N blocks(sectors). > so if cluster size is not page-aligned, > a page may live in non-adjacent blocks, and > do_mpage_readpage has to fall back to block_read_full_page > in this case. But the non-page-aligned clusters can be adjacent on disk, no? Besides, I don't think there's enough overhead in do_mpage_readpage for the non-adjacent case to justify keeping the non-mpage version around. Pekka - 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/