From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Chengwen Feng <fengchengwen@huawei.com>, <thomas@monjalon.net>,
<andrew.rybchenko@oktetlabs.ru>, Ori Kam <orika@nvidia.com>
Cc: <dev@dpdk.org>, <liudongdong3@huawei.com>,
<yisen.zhuang@huawei.com>, <yuying.zhang@intel.com>
Subject: Re: [PATCH 2/2] app/testpmd: add disable-flow-flush parameter
Date: Tue, 31 Jan 2023 13:25:21 +0530 [thread overview]
Message-ID: <50706df4-018b-2b28-2023-4a5ce5a7ced7@intel.com> (raw)
In-Reply-To: <f96a9d85-bf46-5c52-cddb-cff5bcd40751@amd.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On 1/26/2023 12:07 AM, Ferruh Yigit wrote:
> On 12/15/2022 1:41 AM, Chengwen Feng wrote:
>> This patch adds "--disable-flow-flush" parameter, which could used to
>> disable port flow flush when stop port. It allows testing keep flow
>> rules or shared flow objects across restart.
>>
>> Signed-off-by: Chengwen Feng<fengchengwen@huawei.com>
Acked-by: Aman Singh<aman.deep.singh@intel.com>
<snip>
[-- Attachment #2: Type: text/html, Size: 1046 bytes --]
next prev parent reply other threads:[~2023-01-31 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:41 [PATCH 0/2] net/hns3: support rule keep capability Chengwen Feng
2022-12-15 1:41 ` [PATCH 1/2] net/hns3: declare " Chengwen Feng
2022-12-15 1:56 ` Dongdong Liu
2022-12-15 1:41 ` [PATCH 2/2] app/testpmd: add disable-flow-flush parameter Chengwen Feng
2023-01-23 15:01 ` Singh, Aman Deep
2023-01-25 18:34 ` Ferruh Yigit
2023-01-25 18:37 ` Ferruh Yigit
2023-01-26 12:29 ` Ori Kam
2023-01-31 7:55 ` Singh, Aman Deep [this message]
2023-01-31 17:05 ` [PATCH 0/2] net/hns3: support rule keep capability Ferruh Yigit
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=50706df4-018b-2b28-2023-4a5ce5a7ced7@intel.com \
--to=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=liudongdong3@huawei.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yisen.zhuang@huawei.com \
--cc=yuying.zhang@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).