From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jan Beulich <jbeulich@novell.com>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64: improve e820_search_gap()
Date: Sat, 9 May 2009 12:00:08 +0200 [thread overview]
Message-ID: <20090509100008.GD23223@one.firstfloor.org> (raw)
In-Reply-To: <4A049B99.4000402@zytor.com>
> However, as far as querying SRAT, I don't like the idea of spreading the
> knowledge of the system memory map out between a bunch of different
> places, each of which have a little piece of the puzzle. It puts a huge
> onus on the user to know what mechanisms are actually available, and
> really makes a shitty interface.
AFAIK another popular OS always combines mappings from all sources (e820,
SRAT, PCI, PNP, ACPI etc.) in the query before allocating anything.
Something like that might be a reasonable long term direction for Linux
too, but it's probably also a can of worms to handle the conflicts
between the various sources (e.g. e820 reserves a lot of things
in other sources too). It would be a rather large change.
Maybe that would handle the systems I thought of above.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-05-09 9:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 12:07 [PATCH] x86-64: improve e820_search_gap() Jan Beulich
2009-05-08 4:59 ` H. Peter Anvin
2009-05-08 6:40 ` Jan Beulich
2009-05-08 16:52 ` H. Peter Anvin
2009-05-08 19:22 ` Andi Kleen
2009-05-08 20:15 ` H. Peter Anvin
2009-05-08 20:53 ` Andi Kleen
2009-05-08 20:52 ` H. Peter Anvin
2009-05-09 10:00 ` Andi Kleen [this message]
2009-05-10 6:43 ` H. Peter Anvin
2009-05-10 15:18 ` Andi Kleen
2009-05-10 17:56 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2009-03-12 10:45 Jan Beulich
2009-03-12 11:02 ` Ingo Molnar
2009-03-12 11:31 ` Jan Beulich
2009-03-13 17:37 ` Jeremy Fitzhardinge
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=20090509100008.GD23223@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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