From: Shaiq Wani <shaiq.wani@intel.com>
To: dev@dpdk.org, bruce.richardson@intel.com, aman.deep.singh@intel.com
Subject: [PATCH 0/2] net/ice: fix drop rule handling and stats
Date: Thu, 31 Jul 2025 10:11:30 +0530 [thread overview]
Message-ID: <20250731044132.110174-1-shaiq.wani@intel.com> (raw)
Patch 1.Tx packets were dropped when a drop-any rule was applied
only on ingress. A direction lookup flag is added to resolve this.
Patch 2.Added accounting for Rx drop packets in ipackets and ibytes.
Shaiq Wani (2):
net/ice: add flag for direction lookup to occur
net/ice: count drop- all filter stats in Rx stats
drivers/net/intel/ice/base/ice_switch.c | 8 ++++----
drivers/net/intel/ice/ice_ethdev.c | 3 ++-
drivers/net/intel/ice/ice_switch_filter.c | 2 ++
3 files changed, 8 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2025-07-31 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 4:41 Shaiq Wani [this message]
2025-07-31 4:41 ` [PATCH 1/2] net/ice: add flag for direction lookup to occur Shaiq Wani
2025-07-31 4:41 ` [PATCH 2/2] net/ice: count drop- all filter stats in Rx stats Shaiq Wani
2025-07-31 5:43 ` Ivan Malov
2025-07-31 6:03 ` Wani, Shaiq
2025-08-01 0:56 ` zhoumin
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=20250731044132.110174-1-shaiq.wani@intel.com \
--to=shaiq.wani@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).