From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Renata Saiakhova <Renata.Saiakhova@ekinops.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation
Date: Sat, 20 Jun 2020 03:27:46 +0000 [thread overview]
Message-ID: <MWHPR11MB13912D04050BBA1815B6EE44B7990@MWHPR11MB1391.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200513131425.27817-1-Renata.Saiakhova@ekinops.com>
Reviewed-by: Wei Zhao <wei.zhao1@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Renata Saiakhova
> Sent: Wednesday, May 13, 2020 9:14 PM
> To: dev@dpdk.org
> Cc: Renata Saiakhova <Renata.Saiakhova@ekinops.com>
> Subject: [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings
> allocation
>
> igb and ixgbe and some other drivers allocate HW rings using
> rte_eth_dma_zone_reserve(), which checks first if the memzone exists for a
> given name, consisting of port id, queue_id, rx/tx direction, but not for the size,
> alignment, and socket_id.
> If the memzone with a given name exists it is returned, otherwise it is
> allocated.
> Disconnecting dpdk port from one type of interface (igb) and connecting it to
> another type of interface (ixgbe) for the same port id, potentially creates
> memory overlap and corruption, because it may require memzone of bigger
> size.
> That's what is happening from switching from igb to ixgbe having the same port
> id.
>
> v2->v3: Remove #undef ETH_DMA_MZONE_NAME and minor changes in code
> v2->standard
> v1->v2: Minor changes on code standard and additional fixes in i40e em
> v1->and ice drivers
>
> Renata Saiakhova (4):
> librte_ethdev: Introduce a function to release HW rings
> drivers/net: Fix in igb and ixgbe HW rings memory
> drivers/net: Fix in i40e HW rings memory overlap
> drivers/net: Fix in em and ice HW rings memory overlap
>
> drivers/net/e1000/em_rxtx.c | 2 ++
> drivers/net/e1000/igb_rxtx.c | 2 ++
> drivers/net/i40e/i40e_rxtx.c | 2 ++
> drivers/net/ice/ice_rxtx.c | 2 ++
> drivers/net/ixgbe/ixgbe_rxtx.c | 2 ++
> lib/librte_ethdev/rte_ethdev.c | 28 ++++++++++++++++++++++--
> lib/librte_ethdev/rte_ethdev_driver.h | 20 +++++++++++++++++
> lib/librte_ethdev/rte_ethdev_version.map | 1 +
> 8 files changed, 57 insertions(+), 2 deletions(-)
>
> --
> 2.17.2
prev parent reply other threads:[~2020-06-20 3:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:14 Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 1/4] librte_ethdev: Introduce a function to release HW rings Renata Saiakhova
2020-05-14 13:14 ` Burakov, Anatoly
2020-05-15 8:04 ` Jeff Guo
2020-06-19 17:06 ` Ferruh Yigit
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 2/4] drivers/net: Fix in igb and ixgbe HW rings memory Renata Saiakhova
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 3/4] drivers/net: Fix in i40e HW rings memory overlap Renata Saiakhova
2020-06-01 7:58 ` Zhao1, Wei
2020-06-19 16:56 ` Ferruh Yigit
2020-06-20 3:02 ` Zhao1, Wei
2020-05-13 13:14 ` [dpdk-dev] [PATCH v3 4/4] drivers/net: Fix in em and ice " Renata Saiakhova
2020-05-13 15:22 ` [dpdk-dev] [PATCH v3 0/4] Memory corruption due to HW rings allocation Ferruh Yigit
2020-05-18 9:48 ` Renata Saiakhova
2020-06-03 1:36 ` Zhao1, Wei
2020-06-19 16:54 ` Ferruh Yigit
2020-06-19 16:54 ` Ferruh Yigit
2020-06-22 9:59 ` Renata Saiakhova
2020-06-20 3:27 ` Zhao1, Wei [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=MWHPR11MB13912D04050BBA1815B6EE44B7990@MWHPR11MB1391.namprd11.prod.outlook.com \
--to=wei.zhao1@intel.com \
--cc=Renata.Saiakhova@ekinops.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).