64-bit block sizes on 32-bit systems
I vaguely remember a discussion about this a few months back. If I remember, the reasoning was it would unnecessarily slow down smaller systems that would never have block devices in the 4-28T range attached.
However, isn't it possible there will continue to be a series of P-IV,V,VI,VII ...etc, addons that will be used for sometime to come. I've even heard it suggested that we might see 2 or more CPU's on a single chip as a way to increase cpu capacity w/o driving up clock speed. Given the cheapness of .25T drives now, seeing the possibility of 4T drives doesn't seem that remote (maybe 5 years?).
Side question: does the 32-bit block size limit also apply to RAID disks or does it use a different block-nr type?
So...is it the plan, or has it been though about -- 'abstracting' block numbes as a typedef 'block_nr', then at compile time having it be selectable as to whether or not this was to be a 32-bit or 64 bit quantity -- that way older systems would lose no efficiency. Drivers that couldn't be or hadn't been ported to use 'block_nr' could default to being disabled if 64-bit blocks were selected, etc.
So has this idea been tossed about and or previously thrashed?
-l
Signature · 2 lines
L A Walsh | Trust Technology, Core Linux, SGI [email protected] | Voice: (650) 933-5338
Quoted 4 lines · LA Walsh
I vaguely remember a discussion about this a few months back. If I remember, the reasoning was it would unnecessarily slow down smaller systems that would never have block devices in the 4-28T range attached.
4k page size * 2GB = 8TB.
i consider it much more likely on such systems that the page size will be increased to maybe 16 or 64k which would give us 32TB or 128TB. you keep on trying to increase the size of types without looking at what gcc outputs in the way of code that manipulates 64-bit types. seriously, why don't you just try it? see what the performance is. see what the code size is. then come back with some numbers. and i mean numbers, not `it doesn't feel any slower'.
personally, i'm going to see what the situation looks like in 5 years time and try to solve the problem then. there're enough real problems with the VFS today that i don't feel inclined to fix tomorrow's potential problems.
Signature · 1 line
Revolutions do not require corporate support.
Quoted 6 lines · Matthew Wilcox
Quoted 4 lines · LA Walsh
I vaguely remember a discussion about this a few months back. If I remember, the reasoning was it would unnecessarily slow down smaller systems that would never have block devices in the 4-28T range attached.
Quoted 7 lines
4k page size * 2GB = 8TB.
i consider it much more likely on such systems that the page size will be increased to maybe 16 or 64k which would give us 32TB or 128TB.
personally, i'm going to see what the situation looks like in 5 years time and try to solve the problem then.
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
There is some hope with LVM (and MD I suspect as well), that it could do blocksize remapping, so it appears to be a 4k sector device, but remaps to 512-byte sector disks underneath. This _should_ give us an upper limit of 16TB, assuming 32-bit unsigned ints for block numbers. Of course, you would need to only do 4kB block I/O on top of these devices (not much of an issue for such large devices).
Still, this is just a stop-gap measure because next year people will want
Quoted 1 line
16TB devices, and there won't be an easy way to do this.
Cheers, Andreas
Signature · 3 lines
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- DogbertQuoted 5 lines · Andreas Dilger
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Signature · 1 line
Revolutions do not require corporate support.
Quoted 3 lines · Matthew Wilcox
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Sort of. A back-of-the-envelope calculation shows that 2 TB is only 25 80GB IDE drives. Given 4 3ware 8-channel IDE controllers and a large enough case, you could probably build a cheap 2TB RAID0 array for ~$10k. You could do RAID5 for only slightly more.
While this isn't exactly a standard, off-the-shelf, general-purpose sort of configuration, it definately has its uses. Be careful assuming that huge amounts of disk storage requires a huge amount of money, or a high level of reliability or performance.
Scott
Quoted 8 lines · Matthew Wilcox
Quoted 5 lines · Andreas Dilger
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Get real. If you buy (cheapest) 40GB IDE disks, I can have 2TB for U$9200 (not including controllers). In 1 year it will be half, etc. I expect I will start moving my DVD collection to disk storage in an ia32 system once price/GB falls by 50% from current levels. This is just for home use, let alone what large companies want to do. I am fully expecting hard drive price/GB to keep falling at its current rate.
This whole "64-bit" fallacy has got to stop. First it was "anybody who needs files > 2GB should use a 64-bit CPU", wrong. Then it was "anybody who needs > 1GB RAM should use a 64-bit CPU", wrong. Now it is "anybody who needs > 2TB disk should use a 64-bit CPU", soon to be wrong. I don't think the millions of 32-bit systems will disappear overnight, or even in 10 years, yet we already have single IDE disks > 100GB, and in 2 or 3 years we will have single IDE disks > 1TB that people will want to use in their 32-bit systems.
Cheers, Andreas
Signature · 3 lines
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- DogbertQuoted 3 lines · Andreas Dilger
Quoted 1 line · Matthew Wilcox
people who can afford 2TB of disc can afford to buy a 64-bit processor.
This whole "64-bit" fallacy has got to stop.
Indeed.
Quoted 2 lines
Now it is "anybody who needs > 2TB disk should use a 64-bit CPU", soon to be wrong.
It was already wrong in 1995.
-Dan
Quoted 1 line · Matthew Wilcox
people who can afford 2TB of disc can afford to buy a 64-bit processor.
You realise that this'll double the price of storage? ;)
(at least, in a year or two)
Rik
--
Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose...
http://www.surriel.com/
Quoted 8 lines · Matthew Wilcox
Quoted 5 lines · Andreas Dilger
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Currently that doesn't solve the problem as block_nr is held in an int. And as gcc compiles an int to a 32bit number on a 64bit processor, the problem still isn't solved.
That at least we need to address.
Eric
Quoted 10 lines · Eric W. Biederman
Quoted 7 lines · Matthew Wilcox
Quoted 5 lines · Andreas Dilger
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
Quoted 7 lines
Quoted 1 line
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Currently that doesn't solve the problem as
block_nris held in an int. And as gcc compiles an int to a 32bit number on a 64bit processor, the problem still isn't solved.That at least we need to address.
And then you must face the fact that there may be the need for some of the shelf software, which isn't well supported on correspondig 64 bit architectures... as well. So the arguemnt doesn't hold up to the reality in any way. BTW. For many reasons 32 bit architecutres are in respoect of some application shemes *faster* the 64. Ultra III in 64 mode just crawls in comparision to 32. Alpha - unfortulatly an orphaned and dyring archtecutre... which is not well supported by sw verndors...
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Matthew" == Matthew Wilcox <[email protected]> writes:
Matthew> On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger
Quoted 5 lines · Matthew> wrote:
Quoted 5 lines
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
Matthew> people who can afford 2TB of disc can afford to buy a 64-bit Matthew> processor.
Oh great, and migrating a large application to a new architecture is soo cheap. Disk costs nothing these days and there is a legitimate need here.
Jes
Quoted 9 lines · Eric W. Biederman
Quoted 7 lines · Matthew Wilcox
Quoted 5 lines · Andreas Dilger
What do you mean by problems 5 years down the road? The real issue is that this 32-bit block count limit affects composite devices like MD RAID and LVM today, not just individual disks. There have been several postings I have seen with people having a problem _today_ with a 2TB limit on devices.
Quoted 7 lines
Quoted 1 line
people who can afford 2TB of disc can afford to buy a 64-bit processor.
Currently that doesn't solve the problem as
block_nris held in an int. And as gcc compiles an int to a 32bit number on a 64bit processor, the problem still isn't solved.That at least we need to address.
What I don't understand is why we can't just put an option in the Linux config to enable 64-bit block support, as we have with the High Memory Support option. That way the user could select that option if they want it, regardless of the processor they are using. Jens Axboe <[email protected]> already mentioned he had patched the kernel to do someting similar earlier this month on a similar thread on linux-kernel.
It makes sense to have this option when we have an enterprise level LVM and 64-bit file systems such as the Global File System (GFS) for Linux.
Regards,
Signature · 13 lines
AJ Lewis Sistina Software Inc. Voice: 612-379-3951 1313 5th St SE, Suite 111 Fax: 612-379-3952 Minneapolis, MN 55414 E-Mail: [email protected] http://www.sistina.com Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648 Get my key at: http://www.sistina.com/~lewis/gpgkey (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys) -----Begin Obligatory Humorous Quote---------------------------------------- APATHY ERROR: Don't bother striking any key. -----End Obligatory Humorous Quote------------------------------------------
Quoted 4 lines · LA Walsh
I vaguely remember a discussion about this a few months back. If I remember, the reasoning was it would unnecessarily slow down smaller systems that would never have block devices in the 4-28T range attached.
With classic 512 byte sectors the top size is right about 2TB.
The basic thought is that 64bit numbers tend to suck, so we don't want then in any fast paths on a 32bit system.
Quoted 10 lines
However, isn't it possible there will continue to be a series of P-IV,V,VI,VII ...etc, addons that will be used for sometime to come. I've even heard it suggested that we might see 2 or more CPU's on a single chip as a way to increase cpu capacity w/o driving up clock speed. Given the cheapness of .25T drives now, seeing the possibility of 4T drives doesn't seem that remote (maybe 5 years?).
Side question: does the 32-bit block size limit also apply to RAID disks or does it use a different block-nr type?
For now yes it does.
Quoted 10 lines
So...is it the plan, or has it been though about -- 'abstracting' block numbes as a typedef '
block_nr', then at compile time having it be selectable as to whether or not this was to be a 32-bit or 64 bit quantity -- that way older systems would lose no efficiency. Drivers that couldn't be or hadn't been ported to use 'block_nr' could default to being disabled if 64-bit blocks were selected, etc.So has this idea been tossed about and or previously thrashed?
Using a 64bit number of 32bit systems has so far been trashed. Though this does look like a real problem that needs to be solved at some point. I doubt we can wait past 2.5 though if we want the code ready when the hardware is.
Eric
Quoted 4 lines · LA Walsh
So...is it the plan, or has it been though about -- 'abstracting' block numbes as a typedef '
block_nr', then at compile time having it be selectable as to whether or not this was to be a 32-bit or 64 bit quantity -- that way older systems would
Oh, did no-one mention the words `Module ABI' yet?
Signature · 1 line
Revolutions do not require corporate support.