DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Krzysztof Kanas <krzysztof.kanas@caviumnetworks.com>
Cc: dev@dpdk.org, Jerin.JacobKollanukkaran@cavium.com,
	Nithin.Dabilpuram@cavium.com, wenzhuo.lu@intel.com,
	jingjing.wu@intel.com, bernard.iremonger@intel.com,
	cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add commands for TM to mark pkts
Date: Mon, 10 Sep 2018 21:09:39 +0530	[thread overview]
Message-ID: <20180910153938.GA20620@jerin> (raw)
In-Reply-To: <20180817113919.32095-1-krzysztof.kanas@caviumnetworks.com>

-----Original Message-----
> Date: Fri, 17 Aug 2018 13:39:19 +0200
> From: Krzysztof Kanas <krzysztof.kanas@caviumnetworks.com>
> To: dev@dpdk.org
> Cc: krzysztof.kanas@caviumnetworks.com,
>  Jerin.JacobKollanukkaran@cavium.com, Nithin.Dabilpuram@cavium.com
> 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?

  reply	other threads:[~2018-09-10 15:40 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 [this message]
2018-10-02 15:34   ` Iremonger, Bernard
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=20180910153938.GA20620@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=Nithin.Dabilpuram@cavium.com \
    --cc=bernard.iremonger@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --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).