From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] iommu/vt-d: Use ida for domain ID management
Date: Mon, 12 May 2025 14:37:58 +0800 [thread overview]
Message-ID: <2cc8a047-5453-44f1-839e-62425e1ca239@linux.intel.com> (raw)
In-Reply-To: <20250430021135.2370244-1-baolu.lu@linux.intel.com>
On 4/30/25 10:11, Lu Baolu wrote:
> This converts the Intel iommu driver's domain ID management from a
> fixed-size bitmap to the dynamic ida allocator. This improves memory
> efficiency by only allocating resources for the domain IDs actually in
> use, rather than the maximum possible number.
>
> The also includes necessary cleanups after the ida conversion, including
> locking adjustment for the ida.
>
> ---
> Change log:
> v2:
> - Drop the last patch which simplified the code with __free(). There
> needs a helper like xa_store_or_{reset,kfree}(). Thus I plan to put
> it a separated series with broader reviewers.
>
> v1:https://lore.kernel.org/linux-iommu/20250423031020.2189546-1-
> baolu.lu@linux.intel.com/
>
> Lu Baolu (2):
> iommu/vt-d: Use ida to manage domain id
> iommu/vt-d: Replace spin_lock with mutex to protect domain ida
Queued for v6.16-rc1.
prev parent reply other threads:[~2025-05-12 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 2:11 [PATCH v2 0/2] iommu/vt-d: Use ida for domain ID management Lu Baolu
2025-04-30 2:11 ` [PATCH v2 1/2] iommu/vt-d: Use ida to manage domain id Lu Baolu
2025-05-06 17:29 ` Jason Gunthorpe
2025-04-30 2:11 ` [PATCH v2 2/2] iommu/vt-d: Replace spin_lock with mutex to protect domain ida Lu Baolu
2025-05-06 17:29 ` Jason Gunthorpe
2025-05-12 6:37 ` Baolu Lu [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=2cc8a047-5453-44f1-839e-62425e1ca239@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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