All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Lalancette <clalance@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH 3/4] domain heap allocator changes - remove bit width restrictions
Date: Mon, 26 Feb 2007 08:19:24 -0500	[thread overview]
Message-ID: <45E2DE5C.7050808@redhat.com> (raw)
In-Reply-To: <C20524C3.292A%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> It's going to be included in 3.0.5, but I'm not sure what difference that
> makes as to whether or not we limit dom0_mem?
>
>  -- Keir
>
>   

Keir,
     Excuse me if I misunderstood, but I thought these were the patches
to remove the DMA zone that were alluded to in the other thread about
booting Xen on large memory machines.  If they are those patches, then I
don't believe we actually need to limit dom0 memory; since the
constrcut_dom0() allocation will come out of the single large zone, it
should Just Work(tm).  If they aren't those patches, then these have
nothing to do with each other; I apologize for the noise.

Chris Lalancette

  reply	other threads:[~2007-02-26 13: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
2007-02-23 22:16   ` Chris Lalancette
2007-02-23 23:09     ` Keir Fraser
2007-02-26 13:19       ` Chris Lalancette [this message]
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=45E2DE5C.7050808@redhat.com \
    --to=clalance@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jbeulich@novell.com \
    --cc=keir@xensource.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.