From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Will Deacon <will@kernel.org>, <jean-philippe@linaro.org>,
<robin.murphy@arm.com>, <joro@8bytes.org>, <balbirs@nvidia.com>,
<miko.lenczewski@arm.com>, <peterz@infradead.org>,
<kevin.tian@intel.com>, <praan@google.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/7] iommu/arm-smmu-v3: Introduce a per-domain arm_smmu_invs array
Date: Tue, 25 Nov 2025 08:20:17 -0800 [thread overview]
Message-ID: <aSXXQUevF41ATX8g@Asurada-Nvidia> (raw)
In-Reply-To: <20251125134321.GQ153257@nvidia.com>
On Tue, Nov 25, 2025 at 09:43:21AM -0400, Jason Gunthorpe wrote:
> On Mon, Nov 24, 2025 at 08:14:39PM -0800, Nicolin Chen wrote:
> > On Mon, Nov 24, 2025 at 09:42:31PM +0000, Will Deacon wrote:
> > > On Sat, Nov 08, 2025 at 12:08:04AM -0800, Nicolin Chen wrote:
> > > > +VISIBLE_IF_KUNIT
> > > > +struct arm_smmu_invs *arm_smmu_invs_merge(struct arm_smmu_invs *invs,
> > > > + struct arm_smmu_invs *to_merge)
> > > > +{
> > > > + struct arm_smmu_invs *new_invs;
> > > > + struct arm_smmu_inv *new;
> > > > + size_t num_trashes = 0;
> > > > + size_t num_adds = 0;
> > > > + size_t i, j;
> > > > +
> > > > + for (i = j = 0; i < invs->num_invs || j < to_merge->num_invs;) {
> > >
> > > Maybe worth having a simple iterator macro for this?
> >
> > I added two macros:
> >
> > +#define arm_smmu_invs_for_each_inv(invs, idx, inv) \
> > + for (idx = 0, inv = &invs->inv[0]; idx < invs->num_invs; \
> > + inv = &invs->inv[++idx])
> > +#define arm_smmu_invs_for_each_idx_dual(invs1, idx1, invs2, idx2) \
> > + for (idx1 = idx2 = 0; idx1 < invs1->num_invs || idx2 < invs2->num_invs;)
>
> I think pull more stuff in. Something like this:
>
> static inline struct arm_smmu_inv *
> arm_smmu_invs_iter_next(struct arm_smmu_invs *invs, size_t next,
> size_t *idx)
> {
> while (true) {
> if (next >= invs->num_invs) {
> *idx = next;
> return NULL;
> }
> if (!refcount_read(&invs->inv[next].users)) {
> next++;
> continue;
> }
> *idx = next;
> return &invs->inv[next];
> }
> }
>
> static int arm_smmu_inv_cmp(const struct arm_smmu_inv *l,
> const struct arm_smmu_inv *r)
> {
> if (l->smmu != r->smmu)
> return cmp_int((uintptr_t)l->smmu, (uintptr_t)r->smmu);
> if (l->type != r->type)
> return cmp_int(l->type, r->type);
> return cmp_int(l->id, r->id);
> }
>
> static inline int arm_smmu_invs_iter_next_cmp(struct arm_smmu_invs *invs_lhs,
> size_t next_lhs, size_t *idx_lhs,
> struct arm_smmu_invs *invs_rhs,
> size_t next_rhs, size_t *idx_rhs)
> {
> struct arm_smmu_inv *cur_lhs =
> arm_smmu_invs_iter_next(invs_lhs, 0, idx_lhs);
>
> /*
> * Compare of two sorted arrays items. If one side is past the end of
> * the array, return the other side to let it run out the iteration.
> */
> if (!cur_lhs)
> return -1;
> if (next_rhs >= invs_rhs->num_invs)
> return 1;
> return arm_smmu_inv_cmp(cur_lhs, &invs_rhs->inv[next_rhs]);
> }
>
> /*
> * Iterates over all non-trash entries in invs. idx is a stack variable
> * to store the index, cur is a stack variable of 'struct arm_smmu_inv *'
> */
> #define arm_smmu_invs_for_each_inv(invs, idx, cur) \
> for (cur = arm_smmu_invs_iter_next(invs, 0, &(idx)); cur; \
> cur = arm_smmu_invs_iter_next(invs, idx + 1, &(idx)))
>
> /*
> * Iterate over two sorted arrays computing a merge sort
> */
> #define arm_smmu_invs_for_each_merge(invs_lhs, idx_lhs, invs_rhs, idx_rhs, \
> cmp) \
> for (cmp = arm_smmu_invs_iter_next_cmp(invs_lhs, 0, &(idx_lhs), \
> invs_rhs, 0, &(idx_rhs)); \
> idx_lhs < invs_lhs->num_invs || idx_rhs < invs_rhs->num_invs; \
> cmp = arm_smmu_invs_iter_next_cmp( \
> invs_lhs, idx_lhs + (cmp <= 0 ? 1 : 0), &(idx_lhs), \
> invs_rhs, idx_rhs + (cmp >= 0 ? 1 : 0), &(idx_rhs)))
>
>
>
> And then change the loops computing num_trash to work directly on actual things ignoring trash:
>
> arm_smmu_invs_for_each_merge(invs, i, to_merge, j, cmp)
> new_size++;
> new_invs = arm_smmu_invs_alloc(new_size);
Cool. I will integrate this and send v6 today. Thanks for the help!
> Name should probably be for_each_.... though
Hmm, I thought it's more common to see structname_for_each_item,
such as list_for_each_item and xa_for_each?
Thanks
Nicolin
next prev parent reply other threads:[~2025-11-25 16:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 8:08 [PATCH v5 0/7] iommu/arm-smmu-v3: Introduce an RCU-protected invalidation array Nicolin Chen
2025-11-08 8:08 ` [PATCH v5 1/7] iommu/arm-smmu-v3: Explicitly set smmu_domain->stage for SVA Nicolin Chen
2025-11-08 8:08 ` [PATCH v5 2/7] iommu/arm-smmu-v3: Add an inline arm_smmu_domain_free() Nicolin Chen
2025-11-08 8:08 ` [PATCH v5 3/7] iommu/arm-smmu-v3: Introduce a per-domain arm_smmu_invs array Nicolin Chen
2025-11-24 21:42 ` Will Deacon
2025-11-24 22:41 ` Nicolin Chen
2025-11-24 23:03 ` Jason Gunthorpe
2025-11-26 1:07 ` Nicolin Chen
2025-11-25 4:14 ` Nicolin Chen
2025-11-25 13:43 ` Jason Gunthorpe
2025-11-25 16:20 ` Nicolin Chen [this message]
2025-11-08 8:08 ` [PATCH v5 4/7] iommu/arm-smmu-v3: Pre-allocate a per-master invalidation array Nicolin Chen
2025-11-24 21:42 ` Will Deacon
2025-11-24 22:43 ` Nicolin Chen
2025-11-24 23:08 ` Jason Gunthorpe
2025-11-24 23:31 ` Nicolin Chen
2025-11-25 7:43 ` Nicolin Chen
2025-11-25 13:07 ` Jason Gunthorpe
2025-11-08 8:08 ` [PATCH v5 5/7] iommu/arm-smmu-v3: Populate smmu_domain->invs when attaching masters Nicolin Chen
2025-11-24 21:43 ` Will Deacon
2025-11-24 23:13 ` Jason Gunthorpe
2025-11-24 23:19 ` Nicolin Chen
2025-11-26 0:56 ` Nicolin Chen
2025-11-08 8:08 ` [PATCH v5 6/7] iommu/arm-smmu-v3: Add arm_smmu_invs based arm_smmu_domain_inv_range() Nicolin Chen
2025-11-08 8:08 ` [PATCH v5 7/7] iommu/arm-smmu-v3: Perform per-domain invalidations using arm_smmu_invs Nicolin Chen
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=aSXXQUevF41ATX8g@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miko.lenczewski@arm.com \
--cc=peterz@infradead.org \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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).