From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/1] Optimise IOVA allocations for PCI devices
Date: Thu, 12 Oct 2017 12:04:44 +0200 [thread overview]
Message-ID: <20171012100444.GI30803@8bytes.org> (raw)
In-Reply-To: <cda4f03f-acf5-9b74-d8f1-774065bfc94e@semihalf.com>
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?
Regards,
Joerg
next prev parent reply other threads:[~2017-10-12 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 8:52 [PATCH V2 0/1] Optimise IOVA allocations for PCI devices 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 [this message]
2017-10-12 10:08 ` Tomasz Nowicki
2017-10-12 11:14 ` Robin Murphy
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=20171012100444.GI30803@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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).