From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] iommu/io-pgtable-arm: Make allocations NUMA-aware
Date: Tue, 22 May 2018 11:58:13 +0100 [thread overview]
Message-ID: <e338ed0f-e25d-73f3-1afd-1da68a8c1f0f@arm.com> (raw)
In-Reply-To: <20180521184717.GA24025-5wv7dgnIgG8@public.gmane.org>
On 21/05/18 19:47, Will Deacon wrote:
> On Mon, May 21, 2018 at 07:12:40PM +0100, Robin Murphy wrote:
>> We would generally expect pagetables to be read by the IOMMU more than
>> written by the CPU, so in NUMA systems it would be preferable to avoid
>> the IOMMU making cross-node pagetable walks if possible. We already have
>> a handle on the IOMMU device for the sake of coherency management, so
>> it's trivial to grab the appropriate NUMA node when allocating new
>> pagetable pages.
>>
>> Note that we drop the semantics of alloc_pages_exact(), but that's fine
>> since they have never been necessary: the only time we're allocating
>> more than one page is for stage 2 top-level concatenation, but since
>> that is based on the number of IPA bits, the size is always some exact
>> power of two anyway.
>>
>> Signed-off-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
>> ---
>> drivers/iommu/io-pgtable-arm.c | 12 ++++++++----
>> 1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/iommu/io-pgtable-arm.c b/drivers/iommu/io-pgtable-arm.c
>> index 39c2a056da21..e80ca386c5b4 100644
>> --- a/drivers/iommu/io-pgtable-arm.c
>> +++ b/drivers/iommu/io-pgtable-arm.c
>> @@ -231,12 +231,16 @@ static void *__arm_lpae_alloc_pages(size_t size, gfp_t gfp,
>> struct io_pgtable_cfg *cfg)
>> {
>> struct device *dev = cfg->iommu_dev;
>> + int order = get_order(size);
>> + struct page *p;
>> dma_addr_t dma;
>> - void *pages = alloc_pages_exact(size, gfp | __GFP_ZERO);
>> + void *pages;
>>
>> - if (!pages)
>> + p = alloc_pages_node(dev_to_node(dev), gfp | __GFP_ZERO, order);
>> + if (!p)
>> return NULL;
>>
>> + pages = page_address(p);
>
> Might be worth checking/masking out __GFP_HIGHMEM if we see it, since we
> could theoretically run into trouble if we got back a highmem mapping here
> and we're losing the check in __get_free_pages afaict.
True - the only callers are internal ones, and anyone trying to make
inappropriate changes here should quickly discover why highmem doesn't
work without significant surgery all over, but I don't see any harm in
keeping an equivalent VM_BUG_ON as clear documentation.
> Other than than, looks good:
>
> Acked-by: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Thanks!
Robin.
prev parent reply other threads:[~2018-05-22 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 18:12 [PATCH] iommu/io-pgtable-arm: Make allocations NUMA-aware Robin Murphy
[not found] ` <b745ecc2acd6aad20b5c3776ecd58022a9019c91.1526926225.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-05-21 18:47 ` Will Deacon
[not found] ` <20180521184717.GA24025-5wv7dgnIgG8@public.gmane.org>
2018-05-22 10:58 ` Robin Murphy [this message]
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=e338ed0f-e25d-73f3-1afd-1da68a8c1f0f@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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).