All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranjal Shrivastava <praan@google.com>
To: Leo Jiang <leo.jiang1224@foxmail.com>
Cc: Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	joro@8bytes.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu/arm-smmu-v3: Stop queue allocation retry at PAGE_SIZE
Date: Fri, 8 May 2026 14:53:06 +0000	[thread overview]
Message-ID: <af340uhd40FLTaEO@google.com> (raw)
In-Reply-To: <tencent_DA99B62735469A0CD219E9FC73E234A47309@qq.com>

On Wed, Apr 22, 2026 at 05:13:08PM +0800, Leo Jiang wrote:
> Hi Will, Robin,
> 
> Thank you both for the detailed feedback.
> 
> Robin, you are absolutely correct. After a deeper look into the source code,
> I see that allocations smaller than a page are indeed possible in certain
> cases. My previous assumption about the DMA API's granularity was wrong,
> and I appreciate the correction.
> 
> However, as Will noted that the current logic deviates from the original
> intent, I have prepared a v2 to limit the queue allocation retry boundary
> to PAGE_SIZE.
> 
> In v2, I have:
>  - Updated my identity to Leo Jiang.
>  - Removed the code comments as suggested.
> 
> I will send the v2 as a follow-up shortly.

Hi Leo,

The general guidance is to send the v2 as a fresh email so that it
doesn't drop off the commmunity's radar.

Thanks,
Praan



  parent reply	other threads:[~2026-05-08 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18  5:31 [PATCH] iommu/arm-smmu-v3: Stop queue allocation retry at PAGE_SIZE leo.jiang1224
2026-04-21 15:26 ` Will Deacon
2026-04-21 15:56 ` Robin Murphy
2026-04-21 16:38   ` Will Deacon
2026-04-22  9:13     ` Leo Jiang
2026-04-22  9:28       ` [PATCH v2] iommu/arm-smmu-v3: Limit queue allocation retry boundary to PAGE_SIZE Leo Jiang
2026-05-08 14:53       ` Pranjal Shrivastava [this message]
2026-05-09  6:10         ` [PATCH] iommu/arm-smmu-v3: Stop queue allocation retry at PAGE_SIZE Leo Jiang

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=af340uhd40FLTaEO@google.com \
    --to=praan@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=leo.jiang1224@foxmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.