From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 3/4] domain heap allocator changes - remove bit width restrictions
Date: Fri, 23 Feb 2007 18:19:22 +0000 [thread overview]
Message-ID: <C204E0AA.A072%keir@xensource.com> (raw)
In-Reply-To: <45CA164E.76E4.0078.0@novell.com>
On 7/2/07 17:11, "Jan Beulich" <jbeulich@novell.com> wrote:
> Hide the (default or user specified) DMA width from anything outside
> the heap allocator. I/O-capable guests can now request any width for
> the memory they want exchanged/added.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
Applied, but this patch turns the 'heap' list heads in page_alloc.c into a
barking-mad three-dimensional array which will consume over 1MB of BSS on
x86/64! As it happens it also confuses older versions of the PXELinux mboot
module (at least v0.1) which fails to load the dom0 kernel image correctly.
This array is going to have to become a dynamic-allocated and linked
structure. Perhaps:
struct list_head **heap_by_node[MAX_NUMNODES];
heap_by_node[node] = xmalloc_array(struct list_head **, nr_zones);
heap_by_zone = heap_by_node[node]; /* type: list_head ** */
heap_by_zone[zone] = xmalloc_array(struct list_head, MAX_ORDER+1);
heap_by_order = heap_by_zone[zone]; /* type: list_head * */
I.e., a double indirection to get to a particular heap list_head.
Perhaps I'll take a look over the weekend...
-- Keir
next prev parent reply other threads:[~2007-02-23 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:11 [PATCH 3/4] domain heap allocator changes - remove bit width restrictions Jan Beulich
2007-02-23 18:19 ` Keir Fraser [this message]
2007-02-23 22:16 ` Chris Lalancette
2007-02-23 23:09 ` Keir Fraser
2007-02-26 13:19 ` Chris Lalancette
2007-02-26 13:25 ` Keir Fraser
2007-02-26 13:32 ` Chris Lalancette
2007-02-24 12:22 ` Keir Fraser
2007-02-26 8:20 ` Jan Beulich
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=C204E0AA.A072%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.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.