From: Reto Baettig <baettig@scs.ch>
To: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: 64bit offsets for block devices ?
Date: Wed, 06 Dec 2000 06:50:15 -0800 [thread overview]
Message-ID: <3A2E5227.693121F@scs.ch> (raw)
Hi
Imagine we have a virtual disk which provides a 64bit (sparse) address
room. Unfortunately we can not use it as a block device because in a lot
of places (including buffer_head structure), we're using a long or even
an int for the block number.
Is there any way of getting a standardized way of doing I/O to a block
device which could handle 64bit addresses for the block number?
Don't you think that we will run into problems anyway because soon there
will be raid systems with a couple of Terrabytes of space to waste for
mp3's ;-)
Reto
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-06 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 14:50 Reto Baettig [this message]
2000-12-07 4:07 ` 64bit offsets for block devices ? Peter Samuelson
2000-12-07 6:16 ` Brian Pomerantz
2000-12-07 13:24 ` Alan Cox
2000-12-07 16:41 ` Stephen C. Tweedie
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=3A2E5227.693121F@scs.ch \
--to=baettig@scs.ch \
--cc=linux-kernel@vger.kernel.org \
/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