From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Beilei Xing" <beilei.xing@intel.com>,
"Jingjing Wu" <jingjing.wu@intel.com>,
"Qiming Yang" <qiming.yang@intel.com>,
"Qi Zhang" <qi.z.zhang@intel.com>
Cc: <bugzilla@dpdk.org>, <dev@dpdk.org>,
"Olivier Matz" <olivier.matz@6wind.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [Bug 923] i40e PMD contains copy-pasted bug from mempool library
Date: Thu, 20 Jan 2022 10:06:20 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D86E16@smartserver.smartshare.dk> (raw)
In-Reply-To: <bug-923-3@http.bugs.dpdk.org/>
To: i40e, iavf, ice PMD maintainers
CC: mempool library maintainers
> From: bugzilla@dpdk.org [mailto:bugzilla@dpdk.org]
> Sent: Thursday, 20 January 2022 09.43
>
> https://bugs.dpdk.org/show_bug.cgi?id=923
>
> Bug ID: 923
> Summary: i40e PMD contains copy-pasted bug from mempool
> library
> Product: DPDK
> Version: unspecified
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: ethdev
> Assignee: dev@dpdk.org
> Reporter: mb@smartsharesystems.com
> Target Milestone: ---
>
> The mempool library does not flush its cache correctly, but leaves it
> full
> after flushing.
> This bug is fixed in [1], but remains in the i40e PMD, which contains
> copy-pasted code [2] from the mempool library.
>
> Other PMDs with copy-pasted code may have the same bug.
Grep rte_mempool_default_cache could indicate that the AVX512 code in the iavf and ice PMDs also have this bug.
>
> [1]
> http://inbox.dpdk.org/dev/20220119150301.42583-1-
> mb@smartsharesystems.com/T/#u
>
> [2]
> http://code.dpdk.org/dpdk/latest/source/drivers/net/i40e/i40e_rxtx_vec_
> avx512.c#L919
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
next prev parent reply other threads:[~2022-01-20 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 8:43 bugzilla
2022-01-20 9:06 ` Morten Brørup [this message]
2022-07-14 15:46 ` bugzilla
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=98CBD80474FA8B44BF855DF32C47DC35D86E16@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=beilei.xing@intel.com \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--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).