From: "Srivastava, Dheeraj Kumar" <dheerajkumar.srivastava@amd.com>
To: Robin Murphy <robin.murphy@arm.com>, joro@8bytes.org
Cc: will@kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, john.g.garry@oracle.com,
zhangzekun11@huawei.com
Subject: Re: [PATCH 1/2] iommu/iova: Make the rcache depot scale better
Date: Mon, 21 Aug 2023 14:33:04 +0530 [thread overview]
Message-ID: <1f618ab9-389f-e3ec-58fd-fdda14e3b800@amd.com> (raw)
In-Reply-To: <f8c62974-eea8-f58f-cb67-9e2f13b242fd@arm.com>
Hello Robin,
Thanks for the quick reply.
On 8/21/2023 2:25 PM, Robin Murphy wrote:
> Other than that, though, were you able to notice any difference (good or
> bad) in CPU load or memory consumption overall?
I am still in process of testing the patches. I will let you know if any
observe any improvement in CPU load or memory consumption.
Thanks and Regards,
Dheeraj Kumar Srivastava
next prev parent reply other threads:[~2023-08-21 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 17:53 [PATCH 0/2] iommu/iova: Make the rcache depot properly flexible Robin Murphy
2023-08-14 17:53 ` [PATCH 1/2] iommu/iova: Make the rcache depot scale better Robin Murphy
2023-08-21 8:11 ` Srivastava, Dheeraj Kumar
2023-08-21 8:55 ` Robin Murphy
2023-08-21 9:03 ` Srivastava, Dheeraj Kumar [this message]
2023-08-21 12:02 ` John Garry
2023-08-21 12:28 ` Robin Murphy
2023-08-14 17:53 ` [PATCH 2/2] iommu/iova: Manage the depot list size Robin Murphy
2023-08-15 14:11 ` zhangzekun (A)
2023-08-16 4:25 ` Jerry Snitselaar
2023-08-16 16:52 ` Robin Murphy
2023-08-15 10:24 ` [PATCH 0/2] iommu/iova: Make the rcache depot properly flexible John Garry
2023-08-15 11:11 ` Robin Murphy
2023-08-15 13:35 ` John Garry
2023-08-16 15:10 ` Robin Murphy
2023-08-21 11:35 ` John Garry
2023-08-17 16:39 ` Jerry Snitselaar
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=1f618ab9-389f-e3ec-58fd-fdda14e3b800@amd.com \
--to=dheerajkumar.srivastava@amd.com \
--cc=iommu@lists.linux.dev \
--cc=john.g.garry@oracle.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=zhangzekun11@huawei.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®