All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com,
	Tom Hibbert <tom.xen@thoughtcrime.org.nz>
Subject: Re: 3.0.2-testing: pci_set_dma_mask, pci_set_consistent_dma_mask(pci, 0x0fffffff) returns < 0 (ICE1712)
Date: Thu, 13 Apr 2006 15:05:21 -0400	[thread overview]
Message-ID: <1144955122.3422.21.camel@orbit.scot.redhat.com> (raw)
In-Reply-To: <01cd5167b2f3993e1a09c413f1948343@cl.cam.ac.uk>

Hi,

On Thu, 2006-04-13 at 08:46 +0100, Keir Fraser wrote:

> > If the Xen HV runs out of MEMZONE_DMADOM pages, aren't we basically out
> > of luck right now?  Xen guests can't see that shortage, nor does the
> > vmscan.c code have any code to target pages for stealing based on MFN
> > rather than PFN.

> Yes, if that happens then we could be in trouble. Although mostly low 
> memory is allocated for devices only at start of day. 

DomU creation too, if we're using driver domains, I guess.  But that's a
minority case right now.

> The main fly in 
> the ointment is PAE pgds. We get around that right now by reserving a 
> lowmem pool in Xen that normal allocations cannot fall back to.

Right, although that pool defaults to empty unless you manually
configure it.  It would be good if we could avoid the fragility of
requiring custom intervention to set this up.

>  That 
> sorts out most kinds of bad behaviour. We would need the guest kernels 
> to help out with reclamation (at least for guests not on shadow page 
> tables). If Linux had support for hotplug memory (add and remove) I 
> suspect we could make use of that to help out, if we were careful.

Or simply get the balloon driver to target the appropriate pages.  The
problem with using hotplug memory is that that generally works on the
basis of ranges of physical addresses, not machine addresses.  

--Stephen

  reply	other threads:[~2006-04-13 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 12:14 3.0.2-testing: pci_set_dma_mask, pci_set_consistent_dma_mask(pci, 0x0fffffff) returns < 0 (ICE1712) Ian Pratt
2006-04-12 16:55 ` Keir Fraser
2006-04-12 17:15   ` Stephen C. Tweedie
2006-04-12 17:19     ` Keir Fraser
2006-04-12 18:53       ` Stephen C. Tweedie
2006-04-13  7:46         ` Keir Fraser
2006-04-13 19:05           ` Stephen C. Tweedie [this message]
2006-04-14  6:46             ` Keir Fraser
2006-04-14  7:53               ` Molle Bestefich
2006-04-14  8:48                 ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-04-11 11:31 Tom Hibbert

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=1144955122.3422.21.camel@orbit.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=tom.xen@thoughtcrime.org.nz \
    --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.