From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Petr Tesarik <petrtesarik@huaweicloud.com>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
"open list:DMA MAPPING HELPERS" <iommu@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>, petr@tesarici.cz
Subject: Re: [PATCH v1 0/2] swiotlb: Fix a couple of bugs in sizing areas
Date: Mon, 26 Jun 2023 16:08:30 +0200 [thread overview]
Message-ID: <de78e57f7d7ee163f1efdcd1f470eb5ba5e8a060.camel@huaweicloud.com> (raw)
In-Reply-To: <cover.1687784289.git.petr.tesarik.ext@huawei.com>
On Mon, 2023-06-26 at 15:01 +0200, Petr Tesarik wrote:
> From: Petr Tesarik <petr.tesarik.ext@huawei.com>
>
> While reworking the dynamic SWIOTLB implementation, I ran into some
> locking issues with the current implementation. I believe the bugs
> are serious enough to be fixed separately.
Thanks, excellent work!
Reviewed-by: Roberto Sassu <roberto.sassu@huawei.com>
Roberto
> Petr Tesarik (2):
> swiotlb: Always set the number of areas before allocating the pool
> swiotlb: Reduce the number of areas to match actual memory pool size
>
> kernel/dma/swiotlb.c | 46 +++++++++++++++++++++++++++++++++-----------
> 1 file changed, 35 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2023-06-26 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 13:01 Petr Tesarik
2023-06-26 13:01 ` [PATCH v1 1/2] swiotlb: Always set the number of areas before allocating the pool Petr Tesarik
2023-06-26 13:01 ` [PATCH v1 2/2] swiotlb: Reduce the number of areas to match actual memory pool size Petr Tesarik
2023-06-26 14:07 ` [PATCH v1 0/2] swiotlb: Fix a couple of bugs in sizing areas Petr Tesařík
2023-06-29 5:12 ` Christoph Hellwig
2023-06-29 5:44 ` Petr Tesařík
2023-06-26 14:08 ` Roberto Sassu [this message]
2023-06-29 5:10 ` Christoph Hellwig
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=de78e57f7d7ee163f1efdcd1f470eb5ba5e8a060.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=petr@tesarici.cz \
--cc=petrtesarik@huaweicloud.com \
--cc=robin.murphy@arm.com \
--cc=wangkefeng.wang@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®