From: William Park <opengeometry@yahoo.ca>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: blocks or KB?
Date: Thu, 15 Nov 2001 17:04:43 -0500 [thread overview]
Message-ID: <20011115170443.A1533@node0.opengeometry.ca> (raw)
In-Reply-To: <20011115003434.A25883@node0.opengeometry.ca> <200111151235.fAFCZQY31248@oboe.it.uc3m.es> <20011115133133.A732@node0.opengeometry.ca> <20011115131938.M5739@lynx.no>
In-Reply-To: <20011115131938.M5739@lynx.no>; from adilger@turbolabs.com on Thu, Nov 15, 2001 at 01:19:38PM -0700
On Thu, Nov 15, 2001 at 01:19:38PM -0700, Andreas Dilger wrote:
> > Is changing 'int' to 'u64' (and all the dependent code) enough to
> > get 64-bit block devices? I'm willing to do the work.
>
> It is already done, please don't duplicate. Search for 64 bit block
> devices around June of this year for a URL to Jens'/Ben's patch.
> Please repost the URL, as several people have asked.
Found it -- http://people.redhat.com/bcrl/lb/. Strangely, it wasn't
in the linux-kernel list.
--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>.
8 CPU cluster, NAS, (Slackware) Linux, Python, LaTeX, Vim, Mutt, Tin
prev parent reply other threads:[~2001-11-15 22:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:08 what is teh current meaning of blk_size? Peter T. Breuer
2001-11-13 18:51 ` blocks or KB? (was: .. current meaning of blk_size array) Peter T. Breuer
2001-11-14 9:44 ` Martin Dalecki
2001-11-14 20:41 ` Peter T. Breuer
2001-11-14 20:51 ` Martin Dalecki
2001-11-14 21:16 ` Andreas Dilger
2001-11-14 21:49 ` Benjamin LaHaise
2001-11-14 22:33 ` Scott Laird
2001-11-15 1:48 ` William Park
2001-11-15 4:58 ` Andreas Dilger
2001-11-15 5:34 ` William Park
2001-11-15 5:55 ` Andreas Dilger
2001-11-15 10:42 ` Anton Altaparmakov
2001-11-15 12:35 ` Peter T. Breuer
2001-11-15 18:31 ` William Park
2001-11-15 20:19 ` Andreas Dilger
2001-11-15 22:04 ` William Park [this message]
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=20011115170443.A1533@node0.opengeometry.ca \
--to=opengeometry@yahoo.ca \
--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