From: Will Deacon <will@kernel.org>
To: Yong Wu <yong.wu@mediatek.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
srv_heupstream@mediatek.com,
linux-arm-kernel@lists.infradead.org, youlin.pei@mediatek.com,
chao.hao@mediatek.com, anan.sun@mediatek.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Nicolas Boichat <drinkcat@chromium.org>,
Tomasz Figa <tfiga@google.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v2] iommu: Improve the performance for direct_mapping
Date: Mon, 7 Dec 2020 11:05:24 +0000 [thread overview]
Message-ID: <160733817514.2997477.1549939879163904100.b4-ty@kernel.org> (raw)
In-Reply-To: <20201207093553.8635-1-yong.wu@mediatek.com>
On Mon, 7 Dec 2020 17:35:53 +0800, Yong Wu wrote:
> Currently direct_mapping always use the smallest pgsize which is SZ_4K
> normally to mapping. This is unnecessary. we could gather the size, and
> call iommu_map then, iommu_map could decide how to map better with the
> just right pgsize.
>
> >From the original comment, we should take care overlap, otherwise,
> iommu_map may return -EEXIST. In this overlap case, we should map the
> previous region before overlap firstly. then map the left part.
>
> [...]
Applied to arm64 (for-next/iommu/misc), thanks!
[1/1] iommu: Improve the performance for direct_mapping
https://git.kernel.org/arm64/c/093b32a849b3
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2020-12-07 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 9:35 Yong Wu
2020-12-07 11:05 ` Will Deacon [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=160733817514.2997477.1549939879163904100.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anan.sun@mediatek.com \
--cc=catalin.marinas@arm.com \
--cc=chao.hao@mediatek.com \
--cc=drinkcat@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robin.murphy@arm.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.com \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@mediatek.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®