From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jangra, Yogesh" <yogesh.jangra@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"R, Kamalakannan" <kamalakannan.r@intel.com>,
"Suresh Narayane, Harshad" <harshad.suresh.narayane@intel.com>
Subject: RE: [PATCH 0/3] update testsuites that uses softnic driver
Date: Wed, 30 Nov 2022 06:32:13 +0000 [thread overview]
Message-ID: <CY5PR11MB6187D3E781AB46722B8B4D68F5159@CY5PR11MB6187.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221108150636.2459852-1-yogesh.jangra@intel.com>
> -----Original Message-----
> From: Yogesh Jangra <yogesh.jangra@intel.com>
> Sent: Tuesday, November 8, 2022 11:07 PM
> To: dts@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; R, Kamalakannan
> <kamalakannan.r@intel.com>; Suresh Narayane, Harshad
> <harshad.suresh.narayane@intel.com>
> Subject: [PATCH 0/3] update testsuites that uses softnic driver
>
> DPDK 22.11 release has updated the Soft NIC driver. With this release softnic
> is using rte_swx_pipeline_xxx library. The CLI that support flow, metering
> and policing has been removed. So this series removed the
> flow_classify_softnic and metering_and_policing test suites.
> This patch series also update softnic test suite. The testsuite uses the latest
> configuration files.
>
> Yogesh Jangra (3):
> test/metering_and_policing: removed the test suite as per dpdk changes
> test/flow_classify_softnic: removed the test suite as per dpdk changes
> test/softnic: updated softnic test suite as per dpdk 22.11 changes
Applied the series, thanks
prev parent reply other threads:[~2022-11-30 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 15:06 Yogesh Jangra
2022-11-08 15:06 ` [PATCH 1/3] test/metering_and_policing: removed the test suite as per dpdk changes Yogesh Jangra
2022-11-08 15:06 ` [PATCH 2/3] test/flow_classify_softnic: " Yogesh Jangra
2022-11-08 15:06 ` [PATCH 3/3] test/softnic: updated softnic test suite as per dpdk 22.11 changes Yogesh Jangra
2022-11-30 6:32 ` Tu, Lijuan [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=CY5PR11MB6187D3E781AB46722B8B4D68F5159@CY5PR11MB6187.namprd11.prod.outlook.com \
--to=lijuan.tu@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dts@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=kamalakannan.r@intel.com \
--cc=yogesh.jangra@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).