From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>
Cc: "Julian Orth" <ju.orth@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Deak, Imre" <imre.deak@intel.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>
Subject: Re: [PATCH] lib/scatterlist: fix sg_page_count and sg_dma_page_count
Date: Wed, 11 Mar 2026 09:06:48 -0300 [thread overview]
Message-ID: <20260311120648.GV1687929@ziepe.ca> (raw)
In-Reply-To: <IA0PR11MB71859E28938D1695D4223B8AF847A@IA0PR11MB7185.namprd11.prod.outlook.com>
On Wed, Mar 11, 2026 at 06:53:51AM +0000, Kasireddy, Vivek wrote:
> So, given the current situation, what is the right thing to do?
> Should we take your patch that brings back the pages array and treat it as
> a temporary fix until equivalent folio based APIs are available?
IMHO, yes. It saves memory, increases performance, fixes the bug and
uses the APIs properly.
Jason
next prev parent reply other threads:[~2026-03-11 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 13:55 [PATCH] lib/scatterlist: fix sg_page_count and sg_dma_page_count Julian Orth
2026-03-08 16:21 ` Julian Orth
2026-03-08 18:08 ` Jason Gunthorpe
2026-03-08 18:41 ` Julian Orth
2026-03-10 5:49 ` Kasireddy, Vivek
2026-03-10 12:59 ` Jason Gunthorpe
2026-03-11 6:53 ` Kasireddy, Vivek
2026-03-11 12:06 ` Jason Gunthorpe [this message]
2026-03-12 5:44 ` Kasireddy, Vivek
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=20260311120648.GV1687929@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=ju.orth@gmail.com \
--cc=kraxel@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sumit.semwal@linaro.org \
--cc=vivek.kasireddy@intel.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