From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, IanJackson <Ian.Jackson@eu.citrix.com>,
Julien Grall <julien.grall@arm.com>
Subject: Re: [PATCH v2 1/2] page-alloc/x86: don't restrict DMA heap to node 0
Date: Thu, 11 Aug 2016 11:45:17 +0100 [thread overview]
Message-ID: <8996bf20-fd40-32d2-c9cc-d584614d5704@citrix.com> (raw)
In-Reply-To: <57AC733A0200007800104FD1@prv-mh.provo.novell.com>
On 11/08/16 11:44, Jan Beulich wrote:
> When node zero has no memory, the DMA bit width will end up getting set
> to 9, which is obviously not helpful to hold back a reasonable amount
> of low enough memory for Dom0 to use for DMA purposes. Find the lowest
> node with memory below 4Gb instead.
>
> Introduce arch_get_dma_bitsize() to keep this arch-specific logic out
> of common code.
>
> Also adjust the original calculation: I think the subtraction of 1
> should have been part of the flsl() argument rather than getting
> applied to its result. And while previously the division by 4 was valid
> to be done on the flsl() result, this now also needs to be converted,
> as is should only be applied to the spanned pages value.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Julien Grall <julien.grall@arm.com>
> ---
> v2: Extend commit message to reason about the calculation change. Add
> a comment to the calculation.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-11 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 9:17 [PATCH 0/2] NUMA/x86 related adjustments Jan Beulich
2016-08-10 9:23 ` [PATCH 1/2] page-alloc/x86: don't restrict DMA heap to node 0 Jan Beulich
2016-08-10 9:58 ` Andrew Cooper
2016-08-10 10:21 ` Jan Beulich
2016-08-10 12:18 ` Andrew Cooper
2016-08-10 12:50 ` Jan Beulich
2016-08-11 10:44 ` [PATCH v2 " Jan Beulich
2016-08-11 10:45 ` Andrew Cooper [this message]
2016-08-11 9:53 ` [PATCH " Julien Grall
2016-08-11 10:05 ` Jan Beulich
2016-08-10 9:24 ` [PATCH 2/2] x86/NUMA: cleanup Jan Beulich
2016-08-10 10:35 ` Andrew Cooper
2016-08-10 11:47 ` Jan Beulich
2016-08-16 10:02 ` Dario Faggioli
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=8996bf20-fd40-32d2-c9cc-d584614d5704@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).