From: Yi Sun <yi.sun@intel.com>
To: Fenghua Yu <fenghuay@nvidia.com>
Cc: <dave.jiang@intel.com>, <vinicius.gomes@intel.com>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<gordon.jin@intel.com>, <anil.s.keshavamurthy@intel.com>,
<philip.lantz@intel.com>
Subject: Re: [PATCH 2/2] dmaengine: idxd: Add Max SGL Size Support for DSA3.0
Date: Sat, 14 Jun 2025 15:56:03 +0800 [thread overview]
Message-ID: <aE0rE5hhMM1wNk8R@ysun46-mobl.ccr.corp.intel.com> (raw)
In-Reply-To: <a3caf088-3a47-4036-85b6-906141f6b17f@nvidia.com>
On 13.06.2025 15:03, Fenghua Yu wrote:
>Hi, Yi,
>
>On 6/13/25 09:18, Yi Sun wrote:
>>Certain DSA 3.0 opcodes, such as Gather copy and Gather reduce requires max
>s/reduce requires/reduce, require/
>>SGL configured for workqueues prior to support these opcodes.
>s/prior to support/prior to supporting/
>>
Get it.
... ...
>> #define IDXD_DSACAP0_OFFSET 0x180
>> union dsacap0_reg {
>>+ struct {
>>+ u64 max_sgl_shift:4;
>>+ u64 max_gr_block_shift:4;
>>+ u64 ops_inter_domain:7;
>>+ u64 rsvd1:17;
>>+ u64 sgl_formats:16;
>>+ u64 max_sg_process:8;
>>+ u64 rsvd2:8;
>>+ };
>
>Ah. The fields are defined here. I would suggest the fields are
>defined in patch 1 because:
>
>1. Reviewer (like me) may get confused when reviewing patch 1 where
>dsacap0 doesn't have any field but is defined a union.
>
>2. There are fields that not max_sgl_shift. So those fields are
>irrelevant to this patch and had better to be define in patch 1.
>
>> u64 bits;
>> };
>
OK, I see. I'll move this definition to patch 1.
Thanks
--Sun, Yi
prev parent reply other threads:[~2025-06-14 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 16:18 [PATCH 0/2] dmaengine: idxd: Add basic DSA 3.0 capability and SGL support Yi Sun
2025-06-13 16:18 ` [PATCH 1/2] dmaengine: idxd: Expose DSA3.0 capabilities through sysfs Yi Sun
2025-06-13 20:59 ` Dave Jiang
2025-06-14 10:01 ` Yi Sun
2025-06-13 21:43 ` Fenghua Yu
2025-06-13 22:07 ` Fenghua Yu
2025-06-13 22:26 ` Lantz, Philip
2025-06-16 18:08 ` Fenghua Yu
2025-06-19 2:51 ` Sun, Yi
2025-06-13 16:18 ` [PATCH 2/2] dmaengine: idxd: Add Max SGL Size Support for DSA3.0 Yi Sun
2025-06-13 21:00 ` Dave Jiang
2025-06-13 22:03 ` Fenghua Yu
2025-06-14 7:56 ` Yi Sun [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=aE0rE5hhMM1wNk8R@ysun46-mobl.ccr.corp.intel.com \
--to=yi.sun@intel.com \
--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 \
/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