From: Hongfu Li <hongfu.li@linux.dev>
To: Tal Zussman <tz2294@columbia.edu>, Hongfu Li <lihongfu@kylinos.cn>
Cc: hongfu.li@linux.dev, jani.nikula@linux.intel.com,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
kees@kernel.org, tzimmermann@suse.de,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/userptr: Convert page APIs to folio equivalents in put_pages
Date: Fri, 30 Oct 2026 11:06:17 +0800 [thread overview]
Message-ID: <f9110c67-227b-4ab7-98f9-a51703c07352@linux.dev> (raw)
In-Reply-To: <20261029134605.882933-1-tz2294@columbia.edu>
On 10/29/26 9:46 PM, Tal Zussman wrote:
> On Thu, Jul 23, 2026 at 02:46:51PM +0800, Hongfu Li wrote:
>> From: Hongfu Li <lihongfu@kylinos.cn>
>>
>> Cache the folio with page_folio() at the start of the sg_table loop,
>> then use folio helpers directly to eliminate repeated compound_head()
>> lookups inside page API wrappers.
>>
>> Signed-off-by: Hongfu Li <lihongfu@kylinos.cn>
> Hi,
>
> Is there any update on picking this up? It would be great to get this
> in, as it removes the last user of trylock_page() in the tree.
Hi Tal,
You are right, this one never got picked up. I have not received any
review comments on it. It is not abandoned on my side, and if there is
anything that needs fixing, I am happy to send a v2.
> Thanks,
> Tal
--
Best regards,
Hongfu
prev parent reply other threads:[~2026-10-30 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 6:46 [PATCH] drm/i915/userptr: Convert page APIs to folio equivalents in put_pages Hongfu Li
2026-07-23 6:54 ` sashiko-bot
2026-07-23 15:19 ` ✓ i915.CI.BAT: success for " Patchwork
2026-07-24 19:18 ` ✓ i915.CI.Full: " Patchwork
2026-10-29 13:46 ` [PATCH] " Tal Zussman
2026-10-30 3:06 ` Hongfu Li [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=f9110c67-227b-4ab7-98f9-a51703c07352@linux.dev \
--to=hongfu.li@linux.dev \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kees@kernel.org \
--cc=lihongfu@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tz2294@columbia.edu \
--cc=tzimmermann@suse.de \
/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.