public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] delayed disk block allocation
Date: Mon, 04 Mar 2002 00:34:21 -0800	[thread overview]
Message-ID: <3C83318D.D79F887A@zip.com.au> (raw)
In-Reply-To: <3C7F3B4A.41DB7754@zip.com.au> <20020303223103.J4188@lynx.adilger.int> <3C83280A.A8CF7CC8@zip.com.au>, <3C83280A.A8CF7CC8@zip.com.au> <E16hnUV-0000aa-00@starship.berlin>

Daniel Phillips wrote:
> 
> ..
> I guess 4K PAGE_CACHE_SIZE will serve us well for another couple of years,

Having reviewed the archives, it seems that the multipage PAGE_CACHE_SIZE
patches which Hugh and Ben were working on were mainly designed to increase
I/O efficiency.

If that's the only reason for large pages then yeah, I think we can stick
with 4k PAGE_CACHE_SIZE :).  There really are tremendous efficiencies
available in the current code.

Another (and very significant) reason for large pages is to decrease
TLB misses.   Said to be very important for large-working-set scientific
apps and such.  But that doesn't seem to have a lot to do with PAGE_CACHE_SIZE?

> ...
> By the way, have you ever seen a sparse 1K blocksize file?
> ...

Sure I have.  I just created one.  (I'm writing test cases for my
emails now.  Sheesh).

-

  reply	other threads:[~2002-03-04  8:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01  8:26 [patch] delayed disk block allocation Andrew Morton
2002-03-04  2:08 ` Daniel Phillips
2002-03-04  3:10   ` Jeff Garzik
2002-03-04  7:27     ` Andrew Morton
2002-03-04  5:04   ` Mike Fedyk
2002-03-04  5:31     ` Andreas Dilger
2002-03-04  5:40       ` Mike Fedyk
2002-03-04  6:14         ` Andreas Dilger
2002-03-04  5:41       ` Jeff Garzik
2002-03-04  6:18         ` Andreas Dilger
2002-03-04 15:02           ` Hans Reiser
2002-03-06 12:59             ` Pavel Machek
2002-03-04  7:53       ` Andrew Morton
2002-03-04  8:06         ` Daniel Phillips
2002-03-04  8:34           ` Andrew Morton [this message]
2002-03-04  7:20   ` Andrew Morton
2002-03-04  9:23     ` Daniel Phillips
  -- strict thread matches above, loose matches on Subject: below --
2002-03-04 14:54 rwhron
2002-03-04 15:10 ` Jeff Garzik
2002-03-07 12:06 Etienne Lorrain
2002-03-07 14:47 ` Steve Lord
2002-03-07 17:30   ` Mike Fedyk

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=3C83318D.D79F887A@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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