From: David Rientjes <rientjes@google.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org, pasha.tatashin@soleen.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, yosryahmed@google.com,
john.g.garry@oracle.com
Subject: Re: [PATCH v3 2/3] iommu/iova: Reorganise some code
Date: Mon, 5 Feb 2024 10:17:18 -0800 (PST) [thread overview]
Message-ID: <0ffc92e6-9640-293b-8fbf-b2e45badad91@google.com> (raw)
In-Reply-To: <d4753562f4faa0e6b3aeebcbf88fdb60cc22d715.1707144953.git.robin.murphy@arm.com>
On Mon, 5 Feb 2024, Robin Murphy wrote:
> The iova_cache_{get,put}() calls really represent top-level lifecycle
> management for the whole IOVA library, so it's long been rather
> confusing to have them buried right in the middle of the allocator
> implementation details. Move them to a more expected position at the end
> of the file, where it will then also be easier to expand them. With
> this, we can also move the rcache hotplug handler (plus another stray
> function) into the rcache portion of the file.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Acked-by: David Rientjes <rientjes@google.com>
next prev parent reply other threads:[~2024-02-05 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 15:32 [PATCH v3 0/3] iommu/iova: use named kmem_cache for iova magazines Robin Murphy
2024-02-05 15:32 ` [PATCH v3 1/3] iommu/iova: Tidy up iova_cache_get() failure Robin Murphy
2024-02-05 18:15 ` David Rientjes
2024-02-05 18:51 ` Pasha Tatashin
2024-02-06 11:01 ` John Garry
2024-02-06 11:25 ` Robin Murphy
2024-02-07 16:38 ` Jerry Snitselaar
2024-02-05 15:32 ` [PATCH v3 2/3] iommu/iova: Reorganise some code Robin Murphy
2024-02-05 18:17 ` David Rientjes [this message]
2024-02-05 18:51 ` Pasha Tatashin
2024-02-06 11:05 ` John Garry
2024-02-07 16:41 ` Jerry Snitselaar
2024-02-05 15:32 ` [PATCH v3 3/3] iommu/iova: use named kmem_cache for iova magazines Robin Murphy
2024-02-06 11:24 ` John Garry
2024-02-06 11:32 ` Robin Murphy
2024-02-07 16:43 ` Jerry Snitselaar
2024-02-09 10:46 ` [PATCH v3 0/3] " Joerg Roedel
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=0ffc92e6-9640-293b-8fbf-b2e45badad91@google.com \
--to=rientjes@google.com \
--cc=iommu@lists.linux.dev \
--cc=john.g.garry@oracle.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yosryahmed@google.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