From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>
Subject: RE: [PATCH v2 0/3] fix Rx and Tx queue status get
Date: Fri, 14 Jul 2023 03:08:02 +0000 [thread overview]
Message-ID: <DM4PR11MB5994EA979718412B6E94B1C1D734A@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230712083153.3250798-1-qiming.yang@intel.com>
> -----Original Message-----
> From: Yang, Qiming <qiming.yang@intel.com>
> Sent: Wednesday, July 12, 2023 4:32 PM
> To: dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Yang, Qiming <qiming.yang@intel.com>
> Subject: [PATCH v2 0/3] fix Rx and Tx queue status get
>
> 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.
> This issue related commit 141a520b35f7
> app/testpmd: fix primary process not polling all queues
>
> ---
> v2 changes: add CC stable@dpdk.org
>
> 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
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-07-14 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:31 Qiming Yang
2023-07-12 8:31 ` [PATCH v2 1/3] net/ixgbevf: " Qiming Yang
2023-07-12 8:31 ` [PATCH v2 2/3] net/igc: " Qiming Yang
2023-07-12 8:31 ` [PATCH v2 3/3] net/e1000: fix Rx and Tx queue status Qiming Yang
2023-07-14 3:08 ` Zhang, Qi Z [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=DM4PR11MB5994EA979718412B6E94B1C1D734A@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@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).