From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Will Deacon <will@kernel.org>,
Joao Martins <joao.m.martins@oracle.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCHES 1/2] iommu: Add RCU-protected page free support
Date: Fri, 10 Jun 2022 13:37:20 +0800 [thread overview]
Message-ID: <bbada5b7-737f-03dd-7d42-2ebad442a2bb@linux.intel.com> (raw)
In-Reply-To: <20220609124934.GZ1343366@nvidia.com>
On 2022/6/9 20:49, Jason Gunthorpe wrote:
>> +void iommu_free_pgtbl_pages(struct iommu_domain *domain,
>> + struct list_head *pages)
>> +{
>> + struct page *page, *next;
>> +
>> + if (!domain->concurrent_traversal) {
>> + put_pages_list(pages);
>> + return;
>> + }
>> +
>> + list_for_each_entry_safe(page, next, pages, lru) {
>> + list_del(&page->lru);
>> + call_rcu(&page->rcu_head, pgtble_page_free_rcu);
>> + }
> It seems OK, but I wonder if there is benifit to using
> put_pages_list() from the rcu callback
The price is that we need to allocate a "struct list_head" and free it
in the rcu callback as well. Currently the list_head is sitting in the
stack.
Best regards,
baolu
next prev parent reply other threads:[~2022-06-10 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:08 [RFC PATCHES 1/2] iommu: Add RCU-protected page free support Lu Baolu
2022-06-09 7:08 ` [RFC PATCHES 2/2] iommu: Replace put_pages_list() with iommu_free_pgtbl_pages() Lu Baolu
2022-06-09 12:49 ` [RFC PATCHES 1/2] iommu: Add RCU-protected page free support Jason Gunthorpe
2022-06-09 13:19 ` Robin Murphy
2022-06-09 13:32 ` Jason Gunthorpe
2022-06-10 5:59 ` Baolu Lu
2022-06-10 5:37 ` Baolu Lu [this message]
2022-06-15 15:40 ` Jason Gunthorpe
2022-06-16 2:27 ` Baolu Lu
2022-06-20 4:04 ` Jason Gunthorpe
2022-06-09 17:06 ` Raj, Ashok
2022-06-10 6:05 ` Baolu Lu
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=bbada5b7-737f-03dd-7d42-2ebad442a2bb@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--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