From: Robin Murphy <robin.murphy@arm.com>
To: Tomasz Nowicki <tnowicki@caviumnetworks.com>,
Joerg Roedel <joro@8bytes.org>, Tomasz Nowicki <tn@semihalf.com>
Cc: Tomasz Nowicki <tomasz.nowicki@caviumnetworks.com>,
will.deacon@arm.com, Jayachandran.Nair@cavium.com,
ard.biesheuvel@linaro.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Ganapatrao.Kulkarni@cavium.com
Subject: Re: [PATCH V2 0/1] Optimise IOVA allocations for PCI devices
Date: Thu, 12 Oct 2017 12:14:08 +0100 [thread overview]
Message-ID: <c0be8925-a78d-7f9b-99c5-8a812564ce89@arm.com> (raw)
In-Reply-To: <f7210a76-399c-3767-74d0-24a98cbf7d78@caviumnetworks.com>
On 12/10/17 11:08, Tomasz Nowicki wrote:
> Hi Joerg,
>
> On 12.10.2017 12:04, Joerg Roedel wrote:
>> Hi Tomasz,
>>
>> On Thu, Oct 12, 2017 at 11:40:27AM +0200, Tomasz Nowicki wrote:
>>> Can you please have a look and see if you are fine with this patch?
>>
>> How do these changes relate to Robin's IOVA optimizations already in the
>> iommu-tree?
>>
>
> This is another optimization patch which does not conflict with Robin's
> patches.
>
> Robin, please correct me if I am wrong.
Yup, I've had Tomasz' patch included in my iommu/iova branch for a
while, and the "Misc. IOVA tweaks" patches were actually written on top
of it.
This should be the final piece of the puzzle for several arm64 server
platforms, which exacerbate the problem by using 64K pages and having
host bridge windows consume most of the 32-bit mem space.
Robin.
next prev parent reply other threads:[~2017-10-12 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 8:52 Tomasz Nowicki
2017-09-20 8:52 ` [PATCH V2 1/1] iommu/iova: Make rcache flush optional on IOVA allocation failure Tomasz Nowicki
2017-10-12 9:40 ` [PATCH V2 0/1] Optimise IOVA allocations for PCI devices Tomasz Nowicki
2017-10-12 10:04 ` Joerg Roedel
2017-10-12 10:08 ` Tomasz Nowicki
2017-10-12 11:14 ` Robin Murphy [this message]
2017-10-12 12:18 ` Joerg Roedel
2017-10-12 9:41 ` Tomasz Nowicki
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=c0be8925-a78d-7f9b-99c5-8a812564ce89@arm.com \
--to=robin.murphy@arm.com \
--cc=Ganapatrao.Kulkarni@cavium.com \
--cc=Jayachandran.Nair@cavium.com \
--cc=ard.biesheuvel@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tn@semihalf.com \
--cc=tnowicki@caviumnetworks.com \
--cc=tomasz.nowicki@caviumnetworks.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®