From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Aleksandr Miloshenko <a.miloshenko@f5.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/iavf: do Tx done cleanup starting from Tx tail
Date: Tue, 30 Aug 2022 01:45:34 +0000 [thread overview]
Message-ID: <DM4PR11MB5994528C7AAA8D14813B3190D7799@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220830011346.24657-1-a.miloshenko@f5.com>
> -----Original Message-----
> From: Aleksandr Miloshenko <a.miloshenko@f5.com>
> Sent: Tuesday, August 30, 2022 9:14 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Aleksandr Miloshenko <a.miloshenko@f5.com>;
> stable@dpdk.org
> Subject: [PATCH v2] net/iavf: do Tx done cleanup starting from Tx tail
>
> iavf_xmit_pkts() sets tx_tail to the next of last transmitted Tx descriptor. So the
> cleanup of Tx done descriptors must be started from tx_tail, not from the next
> of tx_tail.
> Otherwise rte_eth_tx_done_cleanup() doesn't free the first Tx done mbuf when
> tx queue is full.
>
> Fixes: 86e44244f95c ("net/iavf: cleanup Tx buffers")
> Cc: stable@dpdk.org
>
> Signed-off-by: Aleksandr Miloshenko <a.miloshenko@f5.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2022-08-30 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 0:14 [PATCH] iavf: do tx done cleanup starting from tx_tail Aleksandr Miloshenko
2022-08-30 1:13 ` [PATCH v2] net/iavf: do Tx done cleanup starting from Tx tail Aleksandr Miloshenko
2022-08-30 1:45 ` Zhang, Qi Z [this message]
2022-08-30 1:05 Aleksandr Miloshenko
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=DM4PR11MB5994528C7AAA8D14813B3190D7799@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=a.miloshenko@f5.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@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).