From: Qiming Yang <qiming.yang@intel.com>
To: dev@dpdk.org
Cc: beilei.xing@intel.com, qi.z.zhang@intel.com,
Qiming Yang <qiming.yang@intel.com>
Subject: [PATCH 0/3] fix Rx and Tx queue status get
Date: Wed, 12 Jul 2023 07:42:12 +0000 [thread overview]
Message-ID: <20230712074215.3249336-1-qiming.yang@intel.com> (raw)
Some Intel drivers not support queue start/stop ops, it will caused
application can't get correct queue status and can't forward packets.
This patchset fixed the issue by updating the queue states when the
queue is disabled or enabled.
Qiming Yang (3):
net/ixgbevf: fix Rx and Tx queue status get
net/igc: fix Rx and Tx queue status get
net/e1000: fix Rx and Tx queue status
drivers/net/e1000/igb_rxtx.c | 4 ++++
drivers/net/igc/igc_txrx.c | 4 ++++
drivers/net/ixgbe/ixgbe_rxtx.c | 6 ++++++
3 files changed, 14 insertions(+)
--
2.25.1
next reply other threads:[~2023-07-12 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 7:42 Qiming Yang [this message]
2023-07-12 7:42 ` [PATCH 1/3] net/ixgbevf: " Qiming Yang
2023-07-12 7:42 ` [PATCH 2/3] net/igc: " Qiming Yang
2023-07-12 7:42 ` [PATCH 3/3] net/e1000: fix Rx and Tx queue status Qiming Yang
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=20230712074215.3249336-1-qiming.yang@intel.com \
--to=qiming.yang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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;
as well as URLs for NNTP newsgroup(s).