patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Danylo Vodopianov <dvo-plv@napatech.com>
To: thomas@monjalon.net, aman.deep.singh@intel.com,
	yuying.zhang@intel.com, orika@nvidia.com, mko-plv@napatech.com,
	ckm@napatech.com, dsosnowski@nvidia.com, sil-plv@napatech.com
Cc: getelson@nvidia.com, akozyrev@nvidia.com, dev@dpdk.org,
	stable@dpdk.org, ferruh.yigit@amd.com
Subject: [PATCH v3 0/2] Testpmd flow update/destroy fixes
Date: Mon, 18 Nov 2024 19:03:21 +0100	[thread overview]
Message-ID: <20241118180323.2046886-1-dvo-plv@napatech.com> (raw)
In-Reply-To: <20241118112625.1880659-2-dvo-plv@napatech.com>


These patches provide next fixes:
	1. The testpmd command “flow update…“ provides a nullptr as the
	   context variable.
	2. Avoid removal of additional flows after requested number of flows has
	   been already removed.
v2:
	1. Rephase commit messages.
	2. Copy user_id to the flow list for flow_update command.
	3. Enclose the case's body for flow_destroy command in braces.

v3:
	1. Update commit message
	2. Aligned variable declaration code style

Danylo Vodopianov (2):
  app/testpmd: fix flow update
  app/testpmd: fix aged flow destroy

 app/test-pmd/config.c | 28 +++++++++++++++++++++++++---
 1 file changed, 25 insertions(+), 3 deletions(-)

-- 
2.43.5


  parent reply	other threads:[~2024-11-18 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241031150010.2991953-1-dvo-plv@napatech.com>
2024-11-18 10:25 ` [PATCH v2 " Danylo Vodopianov
2024-11-18 10:25   ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 10:38     ` Dariusz Sosnowski
2024-11-18 10:25   ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 10:43   ` [PATCH v2 0/2] Testpmd flow update/destroy fixes Dariusz Sosnowski
     [not found]     ` <PAWP190MB2160717526F6D67E34952D2E8B272@PAWP190MB2160.EURP190.PROD.OUTLOOK.COM>
2024-11-18 10:59       ` Dariusz Sosnowski
2024-11-18 11:26 ` Danylo Vodopianov
2024-11-18 11:26   ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 12:40     ` Dariusz Sosnowski
2024-11-18 18:02     ` [PATCH v2 0/2] Testpmd flow update/destroy fixes Danylo Vodopianov
2024-11-18 18:02       ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 18:02       ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 18:03     ` Danylo Vodopianov [this message]
2024-11-18 18:03       ` [PATCH v3 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 18:25         ` Dariusz Sosnowski
2024-11-18 18:03       ` [PATCH v3 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 18:25         ` Dariusz Sosnowski
2024-11-19 22:34       ` [PATCH v3 0/2] Testpmd flow update/destroy fixes Thomas Monjalon
2024-11-18 11:26   ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 13:37     ` Dariusz Sosnowski

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=20241118180323.2046886-1-dvo-plv@napatech.com \
    --to=dvo-plv@napatech.com \
    --cc=akozyrev@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=ckm@napatech.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=ferruh.yigit@amd.com \
    --cc=getelson@nvidia.com \
    --cc=mko-plv@napatech.com \
    --cc=orika@nvidia.com \
    --cc=sil-plv@napatech.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).