From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: x86 swiotlb questions
Date: Fri, 15 Dec 2006 14:17:16 +0000 [thread overview]
Message-ID: <4582BC7C.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C1A85BC6.6247%keir@xensource.com>
>>> Keir Fraser <keir@xensource.com> 15.12.06 15:03 >>>
>On 15/12/06 13:53, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> I already have patches ready to do this (the DMA thing really is a nice side
>> effect, I mostly wanted it for 32on64, so that I can restrict domain
>> allocations for 32-bit domains). Are you saying I should throw away the
>> DMA specialization then altogether (I already have no special DMA heap
>> anymore)? The leftovers from it are so that one can reserve some portion
>> of low memory to be returned only when the width restriction is low enough
>> (i.e. to retain dma_emergency_pool functionality), which certainly isn't
>> really appropriate anymore now (it should rather be a percentage or
>> something like that, so that the lower you get the more of the memory
>> remains reserved for specialized allocations).
>
>I think dma_emergency_pool as is can go. Possibly it should be replaced by
>allocator-management tools in dom0 to allow setting of limits on a
>per-bitwidth basis.
Okay, but I think I'll leave this as a separate change (that we probably first
should reach agreement on what it really ought to do and not do).
>Is this one of the patches you already sent in your 32-on-64 batch, or an
>additional one?
An additional one (or actually, a set of them, to make the individual steps
more clear). As a followup, I'm also planning to get rid of the Xen heaps
on those arches where they aren't needed (x86-64, not sure about ppc
and ia64, but I would assume it's really only x86-32 that needs it).
Jan
next prev parent reply other threads:[~2006-12-15 14:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 12:50 x86 swiotlb questions Jan Beulich
2006-12-15 13:35 ` Keir Fraser
2006-12-15 13:53 ` Jan Beulich
2006-12-15 14:03 ` Keir Fraser
2006-12-15 14:17 ` Jan Beulich [this message]
2006-12-15 14:19 ` Keir Fraser
2006-12-15 14:46 ` Jan Beulich
2006-12-15 16:47 ` Keir Fraser
2006-12-15 16:19 ` Alan
2006-12-18 7:44 ` Jan Beulich
2006-12-18 9:39 ` Keir Fraser
2006-12-19 12:48 ` Jan Beulich
2006-12-19 14:14 ` Keir Fraser
2006-12-19 14:39 ` Jan Beulich
2006-12-19 14:46 ` Keir Fraser
2006-12-19 17:07 ` Muli Ben-Yehuda
2006-12-20 16:40 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 14:49 Jan Beulich
2006-12-25 4:50 ` Muli Ben-Yehuda
2006-12-25 10:20 ` Keir Fraser
2006-12-22 16:20 Jan Beulich
2006-12-22 21:00 ` Herbert Xu
2006-12-23 9:48 ` Keir Fraser
2006-12-30 17:32 Jan Beulich
2006-12-30 17:47 ` Keir Fraser
2007-01-02 8:39 ` Jan Beulich
2007-01-03 7:10 ` Jan Beulich
2007-01-03 9:32 ` Keir Fraser
2007-01-03 11:01 ` 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=4582BC7C.76E4.0078.0@novell.com \
--to=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.