From: Gerd Knorr <kraxel@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: xen-devel@lists.xensource.com, Kip Macy <kip.macy@gmail.com>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Wim Coekaerts <wim.coekaerts@oracle.com>,
bill.irwin@oracle.com, Scott Parish <srparish@us.ibm.com>
Subject: Re: understanding __linear_l2_table and friends
Date: Sun, 24 Apr 2005 21:55:22 +0200 [thread overview]
Message-ID: <20050424195522.GA13295@bytesex> (raw)
In-Reply-To: <20050423152826.GG7715@wotan.suse.de>
On Sat, Apr 23, 2005 at 05:28:26PM +0200, Andi Kleen wrote:
> If you bought them in the last year you very likely already got them 64bit
> capable.
That the machines are 64bit capable doesn't mean that people will
actually run 64bit software on them. Note that the very good backward
compatibility of x86_64 machines to 32bit software is one of the key
features leading to the success of the processors (lesson learned from
ia64 ;)
Not everyone will instantly switch over to 64bit software just because
the processor is able to do so, there are still way to much issues with
64bit Software. Linux is way ahead compared to most other operating
systems, and still there are plenty of problems: OpenOffice is still
32bit, Firefox runs in 32bit much more stable than in 64bit, to name
just two prominent examples. And with non-mainstream software it is
even more likely to trap into not-yet fixed 64bit bugs.
Nevertheless I don't expect 80% of the installations being PAE, thats
too much. People will start using 64bit software, but I'm sure not
everybody will not instantly switch over to 64bit just because the
hardware can do that. If it's only to reduce the maintainance work
in a data center with both 32 and 64bit capable machines ...
> In general from my experience working on PAE Linux I can say that the
> complexity of handling more than 4GB RAM with less than 4GB address
> space is often greatly underestimated.
> Of course Xen is simpler than Linux, but in many ways it has much less
> infrastructure to deal with memory pressure so I would not be
> surprised if some stuff would be harder to handle.
Well, after looking into Xen's mm code I'd say this is no problem for
Xen. Xen basically delegates all that work to the guest operating
system, it simply doesn't has to deal with memory pressure issues.
> So the 1 year estimate for it running well might be optimistic.
I'd say it is pessimistic, but let's see ...
At the moment my pae xenlinux kernel doesn't survice paging_init() yet.
It seems to me that this piece of code already triggers almost
everything which must be touched for PAE support in xenlinux and xen
though, so I expect a dom0 multi-user boot isn't that far away once
paging_init() works fine ;)
Gerd
next prev parent reply other threads:[~2005-04-24 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 13:51 understanding __linear_l2_table and friends Ian Pratt
2005-04-21 19:42 ` Gerd Knorr
2005-04-22 11:04 ` Andi Kleen
2005-04-22 20:47 ` Kip Macy
2005-04-23 15:08 ` Andi Kleen
2005-04-23 15:13 ` Wim Coekaerts
2005-04-23 15:28 ` Andi Kleen
2005-04-24 19:55 ` Gerd Knorr [this message]
2005-04-25 0:41 ` David Hopwood
2005-04-25 0:46 ` Mark Williamson
2005-04-25 2:53 ` David Hopwood
2005-04-23 15:20 ` understanding __linear_l2_table and friends II Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 21:13 understanding __linear_l2_table and friends Ian Pratt
2005-04-20 20:27 Ian Pratt
2005-04-20 21:38 ` Gerd Knorr
2005-04-20 22:10 ` Ian Pratt
2005-04-20 18:53 Ian Pratt
2005-04-20 19:14 ` Gerd Knorr
2005-04-20 16:25 Ian Pratt
2005-04-20 16:31 ` Keir Fraser
2005-04-19 23:03 Scott Parish
2005-04-20 10:05 ` Keir Fraser
2005-04-20 16:06 ` Gerd Knorr
2005-04-20 19:46 ` Scott Parish
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=20050424195522.GA13295@bytesex \
--to=kraxel@suse.de \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=bill.irwin@oracle.com \
--cc=kip.macy@gmail.com \
--cc=srparish@us.ibm.com \
--cc=wim.coekaerts@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.