From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Renata Saiakhova <renata.saiakhova@ekinops.com>,
Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] librte_ethdev: Introduce a function to release HW rings
Date: Wed, 6 May 2020 11:14:31 +0100 [thread overview]
Message-ID: <fa71a8fd-13b4-3da5-7661-8e21d4e6b033@intel.com> (raw)
In-Reply-To: <PR0P264MB03324FA393DB6AE0CC6242B692A70@PR0P264MB0332.FRAP264.PROD.OUTLOOK.COM>
On 05-May-20 6:25 PM, Renata Saiakhova wrote:
> Hi Lukasz,
>
> thanks for your comments! I understand Anatoly is going to to make a fix
> rather in memzone API level, to introduce atomic "find and allocate" and
> "find and free" operations, so this patch code won't stay long and in
> this case maybe better not to disturb the original code of
> rte_eth_dma_zone_reserve() ? Just a question.
>
I wouldn't really count on that API appearing in stable any time soon,
so i suggest proceeding with your approach.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-05-06 10:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 16:26 [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation Renata Saiakhova
2020-05-03 16:26 ` [dpdk-dev] [PATCH 1/2] librte_ethdev: Introduce a function to release HW rings Renata Saiakhova
2020-05-05 10:25 ` Burakov, Anatoly
2020-05-05 10:45 ` Burakov, Anatoly
2020-05-05 12:49 ` Renata Saiakhova
2020-05-05 13:36 ` Burakov, Anatoly
2020-05-05 15:47 ` Lukasz Wojciechowski
2020-05-05 17:25 ` Renata Saiakhova
2020-05-05 17:31 ` Lukasz Wojciechowski
2020-05-06 10:14 ` Burakov, Anatoly [this message]
2020-05-03 16:26 ` [dpdk-dev] [PATCH 2/2] drivers/net: Fix in e1000 and ixgbe HW rings memory overlap Renata Saiakhova
2020-05-05 10:28 ` Burakov, Anatoly
2020-05-05 10:59 ` Thomas Monjalon
2020-05-05 11:36 ` Burakov, Anatoly
2020-05-05 11:01 ` [dpdk-dev] [PATCH 0/2] Memory corruption due to HW rings allocation Thomas Monjalon
2020-05-05 11:19 ` Renata Saiakhova
2020-05-05 12:35 ` Thomas Monjalon
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=fa71a8fd-13b4-3da5-7661-8e21d4e6b033@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=l.wojciechow@partner.samsung.com \
--cc=renata.saiakhova@ekinops.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).