From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jens Axboe <axboe@suse.de>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: 64-bit capable block device layer
Date: Thu, 8 Mar 2001 12:14:17 +0000 [thread overview]
Message-ID: <20010308121417.B14121@redhat.com> (raw)
In-Reply-To: <20010307184749.A4653@suse.de> <Pine.LNX.4.33.0103071504250.1409-100000@duckman.distro.conectiva> <20010307195323.D4653@suse.de>
In-Reply-To: <20010307195323.D4653@suse.de>; from axboe@suse.de on Wed, Mar 07, 2001 at 07:53:23PM +0100
Hi,
On Wed, Mar 07, 2001 at 07:53:23PM +0100, Jens Axboe wrote:
> >
> > OTOH, I'm not sure what problems it could give to make this
> > a compile-time option...
>
> Plus compile time options are nasty :-). It would probably make
> bigger sense to completely skip all the merging etc for low end
> machines. I think they already do this for embedded kernels (ie
> removing ll_rw_blk.c and elevator.c). That avoids most of the
> 64-bit arithmetic anyway.
It's not just a sector-number and ll_rw_blk/elevator issue. The limit
goes all the way up to the users of the block device, be they the
filesystem, buffer cache or block read/write layer.
This is especially true for filesystems like XFS which need a 512-byte
blocksize. At least with ext2 you can set the blocksize to 4kB and
get some of the benefit of larger block devices without having to
overflow the 32-bit block number.
Cheers,
Stephen
next prev parent reply other threads:[~2001-03-08 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 17:41 64-bit capable block device layer Rik van Riel
2001-03-07 17:47 ` Jens Axboe
2001-03-07 18:12 ` Rik van Riel
2001-03-07 18:53 ` Jens Axboe
2001-03-08 9:51 ` David Weinehall
2001-03-08 12:14 ` Stephen C. Tweedie [this message]
2001-03-08 13:18 ` Ingo Oeser
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=20010308121417.B14121@redhat.com \
--to=sct@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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