From: Ye Xiaolong <xiaolong.ye@intel.com>
To: taox.zhu@intel.com
Cc: qiming.yang@intel.com, wenzhuo.lu@intel.com, simei.su@intel.com,
yahui.cao@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ice: fix flow fdir/switch memory leak.
Date: Wed, 22 Jan 2020 17:07:54 +0800 [thread overview]
Message-ID: <20200122090754.GE41361@intel.com> (raw)
In-Reply-To: <20200116163836.15696-1-taox.zhu@intel.com>
On 01/16, taox.zhu@intel.com wrote:
>From: Tao Zhu <taox.zhu@intel.com>
>
>1. Fix ice fdir and hash flow memory leak.
>2. Fix the ice definition of LIST_FOR_EACH_ENTRY_SAFE not
> save tmp which cause list deletion incompletely.
>
>Fixes: 5f0978e9622 ("net/ice/base: add OS specific implementation")
>Fixes: f5cafa961fa ("net/ice: add flow director create and destroy")
>Fixes: 5ad3db8d4bd ("net/ice: enable advanced RSS")
>
>Signed-off-by: Tao Zhu <taox.zhu@intel.com>
>Reviewed-by: Su, Simei <simei.su@intel.com>
>Reviewed-by: Cao, Yahui <yahui.cao@intel.com>
>---
Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
Applied to dpdk-next-net-intel, Thanks.
prev parent reply other threads:[~2020-01-22 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 16:38 taox.zhu
2020-01-22 9:07 ` Ye Xiaolong [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=20200122090754.GE41361@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=simei.su@intel.com \
--cc=taox.zhu@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yahui.cao@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).