All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: 64-bit capable block device layer
Date: Wed, 7 Mar 2001 18:47:49 +0100	[thread overview]
Message-ID: <20010307184749.A4653@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0103071432230.1409-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33.0103071432230.1409-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Wed, Mar 07, 2001 at 02:41:17PM -0300

On Wed, Mar 07 2001, Rik van Riel wrote:
> Hi Linus,
> 
> how would you feel about having the block device layer 64-bit
> capable, so Linux can have block devices of more than 2GB in
> size ?
> 
> I know that 64-bit arithmetic is expensive on 32-bit platforms,
> but I have the idea there is a way around that for people who
> don't want 64-bit capable block devices.
> 
> 1. use blkoff_t for all block number arithmetic
> 
> 2. in some header file, have
> 
> #ifdef CONFIG_BLKDEV_64BIT
> typedef long long blkoff_t
> #else
> typedef long blkoff_t
> #endif
> 
> This way, people running smaller&slower machines can chose to
> do the cheaper 32-bit arithmetic and only the people using huge
> block devices will have to do the 64-bit arithmetic.
> 
> (yes, basically the same trick as we're using for PAE)

I already did this here, or something similar at least. Using
a sector_t type that is 64-bit, regardless of platform. Is it
really worth it to differentiate and use 32-bit types for old
machines?

-- 
Jens Axboe


  reply	other threads:[~2001-03-07 17:49 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 [this message]
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
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=20010307184749.A4653@suse.de \
    --to=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 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.