From: Jens Axboe <axboe@suse.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
linux-kernel@vger.kernel.org,
"Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Alexander Viro <viro@math.psu.edu>
Subject: Re: blkdev in pagecache
Date: Wed, 9 May 2001 16:22:48 +0200 [thread overview]
Message-ID: <20010509162248.B521@suse.de> (raw)
In-Reply-To: <20010509043456.A2506@athlon.random> <3AF90A3D.7DD7A605@evision-ventures.com> <20010509151612.D2506@athlon.random> <20010509161452.A521@suse.de> <20010509162009.L2506@athlon.random>
In-Reply-To: <20010509162009.L2506@athlon.random>; from andrea@suse.de on Wed, May 09, 2001 at 04:20:09PM +0200
On Wed, May 09 2001, Andrea Arcangeli wrote:
> On Wed, May 09, 2001 at 04:14:52PM +0200, Jens Axboe wrote:
> > better to stay with PAGE_CACHE_SIZE and not get into dark country :-)
>
> My whole point for not using PAGE_CACHE_SIZE as virtual blocksize is
> that many architectures have a PAGE_CACHE_SIZE > 4k, up to 64k, on
> x86-64 we may even hack a 2M PAGE_SIZE/PAGE_CACHE_SIZE mode for the
> multi giga boxes. I think you agreed I'd better stay to a virtual
> blocksize of 4k fixed for now.
In that case, then yes leaving it as a hardcode 4k would be preferred.
--
Jens Axboe
next prev parent reply other threads:[~2001-05-09 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 2:34 blkdev in pagecache Andrea Arcangeli
2001-05-09 9:13 ` Martin Dalecki
2001-05-09 12:48 ` Jeff Garzik
2001-05-09 15:03 ` Reto Baettig
2001-05-09 15:04 ` Andrea Arcangeli
2001-05-09 13:16 ` Andrea Arcangeli
2001-05-09 14:14 ` Jens Axboe
2001-05-09 14:20 ` Andrea Arcangeli
2001-05-09 14:22 ` Jens Axboe [this message]
2001-05-09 14:43 ` Martin Dalecki
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=20010509162248.B521@suse.de \
--to=axboe@suse.de \
--cc=andrea@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.