From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Bob Picco <bpicco@redhat.com>,
Brian Bloniarz <phunge0@hotmail.com>,
Charles Butterfield <charles.butterfield@nextcentury.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
linux-pci@vger.kernel.org,
"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Stefan Becker <chemobejk@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
Leann Ogasawara <leann.ogasawara@canonical.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v4 6/6] x86: allocate space within a region top-down
Date: Thu, 14 Oct 2010 17:18:52 -0600 [thread overview]
Message-ID: <20101014231852.536.42958.stgit@bob.kio> (raw)
In-Reply-To: <20101014231804.536.62138.stgit@bob.kio>
Request that allocate_resource() use available space from high addresses
first, rather than the default of using low addresses first.
The most common place this makes a difference is when we move or assign
new PCI device resources. Low addresses are generally scarce, so it's
better to use high addresses when possible. This follows Windows practice
for PCI allocation.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228#c42
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
---
arch/x86/kernel/setup.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 922b5a1..0fe76df 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -788,6 +788,7 @@ void __init setup_arch(char **cmdline_p)
x86_init.oem.arch_setup();
+ resource_alloc_from_bottom = 0;
iomem_resource.end = (1ULL << boot_cpu_data.x86_phys_bits) - 1;
setup_memory_map();
parse_setup_data();
next prev parent reply other threads:[~2010-10-14 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 23:18 [PATCH v4 0/6] PCI: allocate space top-down, not bottom-up Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 1/6] resources: ensure alignment callback doesn't allocate below available start Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 2/6] resources: support allocating space within a region from the top down Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 3/6] PCI: allocate bus resources " Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 4/6] x86/PCI: allocate space from the end of a region, not the beginning Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 5/6] x86: update iomem_resource end based on CPU physical address capabilities Bjorn Helgaas
2010-10-14 23:18 ` Bjorn Helgaas [this message]
2010-10-25 21:01 ` [PATCH v4 6/6] x86: allocate space within a region top-down Jesse Barnes
2010-10-25 21:08 ` Bjorn Helgaas
2010-10-25 21:15 ` Bjorn Helgaas
2010-10-25 21:17 ` Jesse Barnes
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=20101014231852.536.42958.stgit@bob.kio \
--to=bjorn.helgaas@hp.com \
--cc=bpicco@redhat.com \
--cc=charles.butterfield@nextcentury.com \
--cc=chemobejk@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=phunge0@hotmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vonbrand@inf.utfsm.cl \
--cc=yinghai@kernel.org \
/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