From: Bruce Richardson <bruce.richardson@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Omar Munchaev <omarmunchaev@gmail.com>, <dev@dpdk.org>,
Omar Munchaev <omar.munchaev@gmail.com>
Subject: Re: [PATCH] net/ice: use macros to get field values
Date: Tue, 6 Oct 2026 16:06:38 +0100 [thread overview]
Message-ID: <asUOfig13OM62UwR@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <86d76bd9-0b96-4304-b8e4-a70814ab7144@intel.com>
On Tue, Oct 06, 2026 at 04:30:00PM +0200, Burakov, Anatoly wrote:
> On 9/28/2026 7:27 PM, Omar Munchaev wrote:
> > Currently, in ice_check_fdir_programming_status,
> > descriptor fields are accessed through direct
> > bit mask manipulation and shifts.
> > The ice driver has macros for this, so rewrite the function
> > to use FIELD_GET macros instead.
> >
> > Signed-off-by: Omar Munchaev <omar.munchaev@gmail.com>
> > ---
> > drivers/net/intel/ice/ice_rxtx.c | 37 ++++++++++++--------------------
> > 1 file changed, 14 insertions(+), 23 deletions(-)
> >
> > diff --git a/drivers/net/intel/ice/ice_rxtx.c b/drivers/net/intel/ice/ice_rxtx.c
> > index 882af80833..f14e5e56b5 100644
> > --- a/drivers/net/intel/ice/ice_rxtx.c
> > +++ b/drivers/net/intel/ice/ice_rxtx.c
> > @@ -4465,36 +4465,27 @@ static inline int
> > ice_check_fdir_programming_status(struct ci_rx_queue *rxq)
> > {
> > volatile union ci_rx_flex_desc *rxdp;
> > - uint16_t qword1;
> > - uint16_t rx_status;
> > - uint16_t error;
> > - uint16_t id;
> > + uint32_t stat_err, error, id
>
> Missing semicolon, so the build fails. Please run
> `devtools/test-meson-builds.sh` script before submission. When submitting
> new versions of the patch, you should increment the version, and the
> patchset also does not have proper threading. Please refer to contribution
> guidelines[1] for how to do this correctly.
>
> [1] https://core.dpdk.org/contribute/
>
> That said, the rest of it looks fine to me, so the semicolon issue can be
> fixed on apply.
>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
Given the missing semicolon, I decided to ask AI to review this patch
before I committed the patch with the small fix. It flags one logic issue
with it:
Finding: FDIR successes are reported as timeouts. In ice_rxtx.c:4469, ret
starts as -EAGAIN and is never set to 0 when a completed descriptor has no
error. The caller treats -EAGAIN as “keep waiting” (ice_rxtx.c:4550), so it
consumes the successful completion, continues polling, and eventually
returns -ETIMEDOUT. Set ret = 0 when DD is present and both failure checks
pass.
This finding looks right to me. ret is set to -EAGAIN at line 4469 and set
to a zero value nowhere else in the function.
/Bruce
next prev parent reply other threads:[~2026-10-06 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 17:27 [PATCH] net/ice: fix missing type casts for flex descriptors Omar Munchaev
2026-09-28 17:27 ` [PATCH] net/ice: use macros to get field values Omar Munchaev
2026-10-06 14:30 ` Burakov, Anatoly
2026-10-06 15:06 ` Bruce Richardson [this message]
2026-10-06 15:09 ` Bruce Richardson
2026-10-06 14:21 ` [PATCH] net/ice: fix missing type casts for flex descriptors Burakov, Anatoly
2026-10-06 14:31 ` Bruce Richardson
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=asUOfig13OM62UwR@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=omar.munchaev@gmail.com \
--cc=omarmunchaev@gmail.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