From: Will Deacon <will@kernel.org>
To: Li RongQing <lirongqing@baidu.com>
Cc: robin.murphy@arm.com, joro@8bytes.org, iommu@lists.linux.dev
Subject: Re: [PATCH][v2] iommu/iova: Consider NUMA affinity when allocating per-CPU iova_magazine
Date: Tue, 30 Apr 2024 16:07:58 +0100 [thread overview]
Message-ID: <20240430150758.GC14187@willie-the-truck> (raw)
In-Reply-To: <20240426051619.10323-1-lirongqing@baidu.com>
On Fri, Apr 26, 2024 at 01:16:19PM +0800, Li RongQing wrote:
> per-CPU iova_magazine are dominantly accessed from their own local CPUs,
> so allocate them node-local for performance reason.
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
> diff with v1: not consider num node in __iova_rcache_insert
>
> drivers/iommu/iova.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
Do you have any numbers showing that this is worthwhile?
Will
prev parent reply other threads:[~2024-04-30 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 5:16 [PATCH][v2] iommu/iova: Consider NUMA affinity when allocating per-CPU iova_magazine Li RongQing
2024-04-30 15:07 ` 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=20240430150758.GC14187@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lirongqing@baidu.com \
--cc=robin.murphy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).