From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <heinrich.kuhn@corigine.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Simon Horman <simon.horman@corigine.com>
Subject: Re: [dpdk-dev] [PATCH] net/nfp: free HW rings memzone on queue release
Date: Wed, 26 Jan 2022 16:53:48 +0000 [thread overview]
Message-ID: <2a077cc2-578a-38c1-3318-a5e84fb3a9db@intel.com> (raw)
In-Reply-To: <20220119114800.6900-1-heinrich.kuhn@corigine.com>
On 1/19/2022 11:48 AM, heinrich.kuhn@corigine.com wrote:
> From: Heinrich Kuhn <heinrich.kuhn@corigine.com>
>
> During rx/tx queue setup, memory is reserved for the hardware rings.
> This memory zone should subsequently be freed in the queue release
> logic. This commit also adds a call to the release logic in the
> dev_close() callback so that the ring memzone may be freed during port
> close too.
>
> Fixes: b812daadad0d ("nfp: add Rx and Tx")
> Cc: stable@dpdk.org
>
> Signed-off-by: Heinrich Kuhn <heinrich.kuhn@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@corigine.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-01-26 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 11:48 heinrich.kuhn
2022-01-26 16:53 ` Ferruh Yigit [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=2a077cc2-578a-38c1-3318-a5e84fb3a9db@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=heinrich.kuhn@corigine.com \
--cc=simon.horman@corigine.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).