[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080625201427.GE6708@one.firstfloor.org>
Date: Wed, 25 Jun 2008 22:14:27 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Keir Fraser <keir.fraser@...citrix.com>
Cc: Andi Kleen <andi@...stfloor.org>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Mark McLoughlin <markmc@...hat.com>,
xen-devel <xen-devel@...ts.xensource.com>,
Eduardo Habkost <ehabkost@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Stephen Tweedie <sct@...hat.com>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support
> There are obviously no x64 boxes around at the moment with >1TB of regular
> shared memory, since no CPUs have more than 40 address lines. 100+TB RAM is
That's actually not true.
> surely years away.
Yes, but why build something non scalable now that you have to fix in a few
years? Especially when it comes with "i have no justification" in
the commit log.
> > So far we always that 64bit Linux can support upto 1/4*max VA memory.
> > With your change that formula would be not true anymore.
>
> Does the formula have any practical significance?
Yes, because getting more than 48bits of VA will be extremly costly
in terms of infrastructure and assuming continuing growth rates and very large
machines 46bits is not all that much.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists