On Wed, Jun 11, 2003 at 07:54:00PM -0400, Christian T. Steigies wrote: > On Thu, Jun 12, 2003 at 01:28:33AM +0200, Michael Banck wrote: > athlon: > Build needed 01:28:10, 3526956k disk space > amd64: 10 minutes? 5? Nah, I don't think the speed difference between similarly clocked Athlon (32) and Opteron is that big a step. >> BTW: The partition limit on GNU/Hurd is 2GB - and there is a buildd >> running usually, too. Well, at least it pretends to :) > I have a 40GB partition on the athlon, I wouldn't expect a limit on > amd64 then? No, the limit comes from the way the Hurd ext2fs translator (think "the Hurd ext2 filesystem implementation") works: It is a normal, non-privileged process, and it maps the whole partition (the /dev/hdXsY file) into its virtual memory space. Which fails if there isn't enough virtual memory space, like on 32 bit machines with current HD's. It is currently being re-implemented to use a caching strategy instead, I believe. As long as you are using Linux, you won't have such limitations cropping up from new architectures (but others may, wrt to page size, I think the Linux ext2 code cannot handle block sizes bigger than page size or something like that. But I wouldn't expect new architectures to have smaller page sizes than old one.). -- Lionel
Attachment:
pgpIoQ179qsSv.pgp
Description: PGP signature