From: Andrea Arcangeli <andrea@suse.de>
To: Reto Baettig <baettig@scs.ch>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
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>, Jens Axboe <axboe@suse.de>
Subject: Re: blkdev in pagecache
Date: Wed, 9 May 2001 17:04:16 +0200 [thread overview]
Message-ID: <20010509170416.U2506@athlon.random> (raw)
In-Reply-To: <20010509043456.A2506@athlon.random> <3AF90A3D.7DD7A605@evision-ventures.com> <3AF93CA2.F2E8C5DB@mandrakesoft.com> <3AF95C2A.1765681E@scs.ch>
In-Reply-To: <3AF95C2A.1765681E@scs.ch>; from baettig@scs.ch on Wed, May 09, 2001 at 05:03:06PM +0200
On Wed, May 09, 2001 at 05:03:06PM +0200, Reto Baettig wrote:
> Jeff Garzik schrieb:
> >
> > Martin Dalecki wrote:
> > > > - I force the virtual blocksize for all the blkdev I/O
> > > > (buffered and direct) to work with a 4096 bytes granularity instead of
> > >
> > > You mean PAGE_SIZE :-).
>
> Or maybe 8192 bytes on alphas ?!? ;-)
Again, see my argument with Jens, if we make it 8k we risk triggering
lowlevel driver assumption about b_size being <= 4k. At least on my
alpha the fs has a 4k blocksize and I think I never tested myself using
a b_size of 8k yet and so I didn't wanted to put too many unknown
variables into the first equation ;).
Andrea
next prev parent reply other threads:[~2001-05-09 15:05 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 [this message]
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
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=20010509170416.U2506@athlon.random \
--to=andrea@suse.de \
--cc=axboe@suse.de \
--cc=baettig@scs.ch \
--cc=dalecki@evision-ventures.com \
--cc=jgarzik@mandrakesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox