From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Krzysztof Kanas <krzysztof.kanas@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Jerin.JacobKollanukkaran@cavium.com"
<Jerin.JacobKollanukkaran@cavium.com>,
"Nithin.Dabilpuram@cavium.com" <Nithin.Dabilpuram@cavium.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add commands for TM to mark pkts
Date: Tue, 2 Oct 2018 15:34:22 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C260D0BBCC@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <20180910153938.GA20620@jerin>
Hi Jerin
<snip>
> > Subject: [dpdk-dev] [PATCH] app/testpmd: add commands for TM to mark
> > pkts
> > X-Mailer: git-send-email 2.18.0
> >
> > Add following testpmd run-time commands to support test of TM packet
> > marking:
> >
> > set port tm mark ip_ecn <port_id> <green> <yellow> <red>
> > set port tm mark ip_dscp <port_id> <green> <yellow> <red> set port tm
> > mark vlan_dei <port_id> <green> <yellow> <red>
> >
> > Signed-off-by: Krzysztof Kanas <krzysztof.kanas@caviumnetworks.com>
> > ---
> > app/test-pmd/cmdline.c | 3 +
> > app/test-pmd/cmdline_tm.c | 260 ++++++++++++++++++++
> > app/test-pmd/cmdline_tm.h | 3 +
>
> + Cristian, Wenzhuo, Jingjing, Bernard
>
> In addition to this slow path change, IMO, we need test engine similar to
> checksum(app/test-pmd/csumonly.c) to generate traffic(app/test-
> pmd/markonly.c) with struct rte_mbuf::tx_offload populated so that we can test
> the packet marking.
>
> Cristian,
>
> Any thoughts as a rte_tm maintainer?
I would suggest someone familiar with the Traffic Management code as a maintainer for the TM code in testpmd.
Regards,
Bernard.
next prev parent reply other threads:[~2018-10-02 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 11:39 Krzysztof Kanas
2018-09-10 15:39 ` Jerin Jacob
2018-10-02 15:34 ` Iremonger, Bernard [this message]
2018-10-08 16:04 ` Dumitrescu, Cristian
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=8CEF83825BEC744B83065625E567D7C260D0BBCC@IRSMSX107.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=Jerin.JacobKollanukkaran@cavium.com \
--cc=Nithin.Dabilpuram@cavium.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jingjing.wu@intel.com \
--cc=krzysztof.kanas@caviumnetworks.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).