DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Ori Kam <orika@mellanox.com>, Bill Zhou <dongz@mellanox.com>,
	"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	 "beilei.xing@intel.com" <beilei.xing@intel.com>,
	"bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] app/testpmd: support flow aging
Date: Wed, 6 May 2020 08:04:30 +0000	[thread overview]
Message-ID: <AM0PR0502MB40198D243CB5AB13C09C2500D2A40@AM0PR0502MB4019.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <ee95e470-8a72-ec55-3d16-dd9838191e62@intel.com>



From: Ferruh Yigit:
> On 5/5/2020 11:09 AM, Ori Kam wrote:
> >
> >
> >> -----Original Message-----
> >> From: Bill Zhou <dongz@mellanox.com>
> >> Sent: Tuesday, May 5, 2020 12:49 PM
> >> Subject: [PATCH v5] app/testpmd: support flow aging
> >>
> >> Currently, there is no way to check the aging event or to get the
> >> current aged flows in testpmd, this patch include those implements, it's
> included:
> >>
> >> - Add new item "flow_aged" to the current print event command
> arguments.
> >> - Add new command to list all aged flows, meanwhile, we can set
> parameter
> >>   to destroy it.
> >>
> >> Signed-off-by: Bill Zhou <dongz@mellanox.com>
> >> ---
> >> v2: Update the way of registering aging event, add new command to
> >> control if the event need be print or not. Update the output of the
> >> delete aged flow command format.
> >> v3: Change the command from only set aged flow output to set one
> >> gloable verbose bitmap for all events output.
> >> v4: Add the event output to current global print event arguments.
> >> v5: Update the documentation about print event command line change.
> >>  app/test-pmd/cmdline.c                      |   4 +
> >>  app/test-pmd/cmdline_flow.c                 |  62 +++++++++++
> >>  app/test-pmd/config.c                       | 108 ++++++++++++++++++--
> >>  app/test-pmd/parameters.c                   |   6 +-
> >>  app/test-pmd/testpmd.c                      |   4 +-
> >>  app/test-pmd/testpmd.h                      |   3 +
> >>  doc/guides/testpmd_app_ug/run_app.rst       |   4 +-
> >>  doc/guides/testpmd_app_ug/testpmd_funcs.rst |  62 +++++++++++
> >>  8 files changed, 237 insertions(+), 16 deletions(-)
> >>
> >
> > Acked-by: Ori Kam <orika@mellanox.com>
> 
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Matan Azrad <matan@mellanox.com>
> Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-05-06  8:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:55 [dpdk-dev] [PATCH] " Bill Zhou
2020-04-24 16:25 ` Ferruh Yigit
2020-04-26  7:23   ` Bill Zhou
2020-04-27 14:13     ` Ferruh Yigit
2020-04-27 15:12       ` Matan Azrad
2020-04-30 22:26         ` Ferruh Yigit
2020-04-30 15:53 ` [dpdk-dev] [PATCH v2] " Bill Zhou
2020-04-30 22:43   ` Ferruh Yigit
2020-05-01  6:51     ` Matan Azrad
2020-05-01  9:27       ` Ferruh Yigit
2020-05-01 11:28         ` Matan Azrad
2020-05-01 11:54           ` Ferruh Yigit
2020-05-01 12:45             ` Matan Azrad
2020-05-01 13:38               ` Ferruh Yigit
2020-05-01 15:14                 ` Matan Azrad
2020-05-01 15:44                   ` Ferruh Yigit
2020-05-02 14:00   ` [dpdk-dev] [PATCH v3] " Bill Zhou
2020-05-03  8:59     ` [dpdk-dev] [PATCH v4] " Bill Zhou
2020-05-03  9:46       ` Matan Azrad
2020-05-03 14:58       ` Ori Kam
2020-05-05  8:37       ` Ferruh Yigit
2020-05-05  9:11         ` Matan Azrad
2020-05-05  9:23           ` Ferruh Yigit
2020-05-05  9:49       ` [dpdk-dev] [PATCH v5] " Bill Zhou
2020-05-05 10:09         ` Ori Kam
2020-05-05 15:11           ` Ferruh Yigit
2020-05-06  8:04             ` Matan Azrad [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=AM0PR0502MB40198D243CB5AB13C09C2500D2A40@AM0PR0502MB4019.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=beilei.xing@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=dongz@mellanox.com \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=orika@mellanox.com \
    --cc=wenzhuo.lu@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).