public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: fs block size and PAGE_CACHE_SIZE
Date: Mon, 12 May 2003 09:59:36 +0800	[thread overview]
Message-ID: <3EBF0008.5020306@shaolinmicro.com> (raw)
In-Reply-To: OFF425B5FA.4C85C6AF-ON87256D1E.00731090-88256D1E.0073F46C@us.ibm.com

Bryan Henderson wrote:

>
>
>I don't know why there would be any issue having page size != block size,
>as long as one is a multiple of the other.  Maybe you have a particular
>issue in mind?
>
>I know one area where having a block larger than a page is a pain:  When
>you allocate a new block in order to write just one page, you have to
>separately initialize the rest of the block.
>
>  
>
>>how could I efficient populate one 16k block to page cache(4 pages) at one
>>    
>>
>readpage() op?
>
>Why would you want to?  If someone wants to access those other 3 pages,
>they'll have page faults of their own.
>  
>
Yes, for uncompressed file systems it doesn't really matter. If I am 
writing a file system that supports 16k blocks compression, I have to 
spend 3 extra (12k extra) compression work for only one 4k data. Since 
there is no way for me to read in the middle of the block. If the extra 
12k data read from the block didn't put into page cache and set 
up-to-date, it will be wasted. That's why.

regards,
David Chow


  parent reply	other threads:[~2003-05-12  1:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 17:42 fs block size and PAGE_CACHE_SIZE David Chow
2003-05-06 19:34 ` Szakacsits Szabolcs
2003-05-06 21:08 ` Bryan Henderson
2003-05-07  0:59   ` Phillip Lougher
2003-05-12  1:59   ` David Chow [this message]
2003-05-06 21:34 ` Trond Myklebust
     [not found]   ` <3EBE85E8.50906@shaolinmicro.com>
2003-05-12  0:31     ` Trond Myklebust
2003-05-12  2:07       ` David Chow
2003-05-12 10:32         ` Anton Altaparmakov
2003-05-12 11:33         ` Phillip Lougher
2003-05-12 17:46           ` David Chow
2003-05-07  0:48 ` Phillip Lougher
2003-05-11 17:12   ` David Chow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EBF0008.5020306@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox