mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Ganapatrao Kulkarni <gklkml16@gmail.com>
Cc: Joerg Roedel <joro@8bytes.org>, Christoph Hellwig <hch@lst.de>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	Robin Murphy <robin.murphy@arm.com>,
	<iommu@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linuxarm <linuxarm@huawei.com>, Will Deacon <will.deacon@arm.com>,
	"Ganapatrao Kulkarni" <ganapatrao.kulkarni@cavium.com>
Subject: Re: [PATCH] iommu/dma: Use NUMA aware memory allocations in __iommu_dma_alloc_pages()
Date: Tue, 20 Nov 2018 10:19:22 +0000	[thread overview]
Message-ID: <be6141f0-ae12-378c-9628-dee306f803cf@huawei.com> (raw)
In-Reply-To: <CAKTKpr4S_v+Fm9K0F8xZTuwKSArZapXr-4Xo1YoNn8=X70H83g@mail.gmail.com>

On 20/11/2018 10:09, Ganapatrao Kulkarni wrote:
> Hi John,
>
> On Tue, Nov 20, 2018 at 3:35 PM John Garry <john.garry@huawei.com> wrote:
>>
>> On 08/11/2018 17:55, John Garry wrote:
>>> Change function __iommu_dma_alloc_pages() to allocate memory/pages
>>> for DMA from respective device NUMA node.
>>>
>>
>> Ping.... a friendly reminder on this patch.
>>
>> Thanks
>>
>>> Originally-from: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
>>> Signed-off-by: John Garry <john.garry@huawei.com>
>>> ---
>>>
>>> This patch was originally posted by Ganapatrao in [1] *.
>>>
>>> However, after initial review, it was never reposted (due to lack of
>>> cycles, I think). In addition, the functionality in its sibling patches
>>> were merged through patches, as mentioned in [2]; this also refers to a
>>> discussion on device local allocations vs CPU local allocations for DMA
>>> pool, and which is better [3].
>>>
>>> However, as mentioned in [3], dma_alloc_coherent() uses the locality
>>> information from the device - as in direct DMA - so this patch is just
>>> applying this same policy.
>>>
>>> [1] https://lore.kernel.org/patchwork/patch/833004/
>>> [2] https://lkml.org/lkml/2018/8/22/391
>>> [3] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1692998.html
>>>
>>> * Authorship on this updated patch may need to be fixed - I add not want to
>>>   add Ganapatrao's SOB without permission.
>
> thanks for taking this up. please feel free to add my SoB.

OK, I will also make you the author and repost.

Thanks,
John

>>>
>>> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
>>> index d1b0475..ada00bc 100644
>>> --- a/drivers/iommu/dma-iommu.c
>>> +++ b/drivers/iommu/dma-iommu.c
>>> @@ -449,20 +449,17 @@ static void __iommu_dma_free_pages(struct page **pages, int count)
>>>       kvfree(pages);
>>>  }
>>>
>>> -static struct page **__iommu_dma_alloc_pages(unsigned int count,
>>> -             unsigned long order_mask, gfp_t gfp)
>>> +static struct page **__iommu_dma_alloc_pages(struct device *dev,
>>> +             unsigned int count, unsigned long order_mask, gfp_t gfp)
>>>  {
>>>       struct page **pages;
>>> -     unsigned int i = 0, array_size = count * sizeof(*pages);
>>> +     unsigned int i = 0, nid = dev_to_node(dev);
>>>
>>>       order_mask &= (2U << MAX_ORDER) - 1;
>>>       if (!order_mask)
>>>               return NULL;
>>>
>>> -     if (array_size <= PAGE_SIZE)
>>> -             pages = kzalloc(array_size, GFP_KERNEL);
>>> -     else
>>> -             pages = vzalloc(array_size);
>>> +     pages = kvzalloc_node(count * sizeof(*pages), GFP_KERNEL, nid);
>>>       if (!pages)
>>>               return NULL;
>>>
>>> @@ -483,8 +480,10 @@ static struct page **__iommu_dma_alloc_pages(unsigned int count,
>>>                       unsigned int order = __fls(order_mask);
>>>
>>>                       order_size = 1U << order;
>>> -                     page = alloc_pages((order_mask - order_size) ?
>>> -                                        gfp | __GFP_NORETRY : gfp, order);
>>> +                     page = alloc_pages_node(nid,
>>> +                                             (order_mask - order_size) ?
>>> +                                             gfp | __GFP_NORETRY : gfp,
>>> +                                             order);
>>>                       if (!page)
>>>                               continue;
>>>                       if (!order)
>>> @@ -569,7 +568,8 @@ struct page **iommu_dma_alloc(struct device *dev, size_t size, gfp_t gfp,
>>>               alloc_sizes = min_size;
>>>
>>>       count = PAGE_ALIGN(size) >> PAGE_SHIFT;
>>> -     pages = __iommu_dma_alloc_pages(count, alloc_sizes >> PAGE_SHIFT, gfp);
>>> +     pages = __iommu_dma_alloc_pages(dev, count, alloc_sizes >> PAGE_SHIFT,
>>> +                                     gfp);
>>>       if (!pages)
>>>               return NULL;
>>>
>>>
>>
>>
>
> thanks
> Ganapat
>
> .
>



      reply	other threads:[~2018-11-20 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 17:55 John Garry
2018-11-20  9:57 ` John Garry
2018-11-20 10:09   ` Ganapatrao Kulkarni
2018-11-20 10:19     ` John Garry [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=be6141f0-ae12-378c-9628-dee306f803cf@huawei.com \
    --to=john.garry@huawei.com \
    --cc=ganapatrao.kulkarni@cavium.com \
    --cc=gklkml16@gmail.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®