From mboxrd@z Thu Jan  1 00:00:00 1970
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: fs block size and PAGE_CACHE_SIZE
Date: 06 May 2003 23:34:49 +0200
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <shs8ytjyd1i.fsf@charged.uio.no>
References: <3EB7F401.1010908@shaolinmicro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from pat.uio.no ([129.240.130.16]:41982 "EHLO pat.uio.no")
	by vger.kernel.org with ESMTP id S261932AbTEFVWW (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 6 May 2003 17:22:22 -0400
To: David Chow <davidchow@shaolinmicro.com>
In-Reply-To: <3EB7F401.1010908@shaolinmicro.com>
List-Id: linux-fsdevel.vger.kernel.org

>>>>> " " == David Chow <davidchow@shaolinmicro.com> writes:

     > In other words, is it possible (or someone already done) to
     > implement a file system that has 16k block size on a 4k paging
     > system.

The NFS client does that. In 2.4.x, I had to invent a custom system
for coalescing the pages, but in 2.5.x, Andrew added the readpages()
op, and the ability to control page readahead via the backing_dev_info
struct.

Cheers,
  Trond