From: Vinod Koul <vkoul@kernel.org>
To: Yi Sun <yi.sun@intel.com>
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
dave.jiang@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, fenghuay@nvidia.com,
philip.lantz@intel.com, gordon.jin@intel.com,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH v2 2/2] dmaengine: idxd: Add Max SGL Size Support for DSA3.0
Date: Wed, 20 Aug 2025 23:00:44 +0530 [thread overview]
Message-ID: <aKYGRC2TzHpnhRyO@vaman> (raw)
In-Reply-To: <aJqizVCcYSL-4LOm@ysun46-mobl.ccr.corp.intel.com>
On 12-08-25, 10:11, Yi Sun wrote:
> On 23.06.2025 17:41, Vinicius Costa Gomes wrote:
> > Yi Sun <yi.sun@intel.com> writes:
> >
> > > Certain DSA 3.0 opcodes, such as Gather copy and Gather reduce, require max
> > > SGL configured for workqueues prior to supporting these opcodes.
> > >
> > > Configure the maximum scatter-gather list (SGL) size for workqueues during
> > > setup on the supported HW. Application can then properly handle the SGL
> > > size without explicitly setting it.
> > >
> > > Signed-off-by: Yi Sun <yi.sun@intel.com>
> > > Co-developed-by: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
> > > Signed-off-by: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
> > > Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> > >
> >
> > Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> >
> >
> > Cheers,
> > --
> > Vinicius
>
> Hi Vinod,
>
> Gentle ping on the entire series.
Can you please rebase and resend this
--
~Vinod
next prev parent reply other threads:[~2025-08-20 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:09 [PATCH v2 0/2] dmaengine: idxd: Add basic DSA 3.0 capability and SGL support Yi Sun
2025-06-20 13:09 ` [PATCH v2 1/2] dmaengine: idxd: Expose DSA3.0 capabilities through sysfs Yi Sun
2025-06-24 0:40 ` Vinicius Costa Gomes
2025-06-20 13:09 ` [PATCH v2 2/2] dmaengine: idxd: Add Max SGL Size Support for DSA3.0 Yi Sun
2025-06-24 0:41 ` Vinicius Costa Gomes
2025-08-12 2:11 ` Yi Sun
2025-08-20 17:30 ` Vinod Koul [this message]
2025-08-21 4:36 ` Sun, Yi
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=aKYGRC2TzHpnhRyO@vaman \
--to=vkoul@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghuay@nvidia.com \
--cc=gordon.jin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.lantz@intel.com \
--cc=vinicius.gomes@intel.com \
--cc=yi.sun@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