From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: nikhil.rao@intel.com, anoob.joseph@caviumnetworks.com,
dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v3 4/4] doc: update eventdev application guide
Date: Sun, 23 Sep 2018 16:16:37 +0530 [thread overview]
Message-ID: <20180923104636.GC20954@jerin> (raw)
In-Reply-To: <20180919222235.6239-4-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Thu, 20 Sep 2018 03:52:35 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, nikhil.rao@intel.com,
> anoob.joseph@caviumnetworks.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
> john.mcnamara@intel.com
> Subject: [dpdk-dev] [PATCH v3 4/4] doc: update eventdev application guide
> X-Mailer: git-send-email 2.18.0
>
> Update eventdev application guide to reflect Tx adapter related changes.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
> cc: <john.mcnamara@intel.com>
>
> .../eventdev_pipeline_atq_test_generic.svg | 848 +++++++++++-------
> ...ntdev_pipeline_atq_test_internal_port.svg} | 26 +-
> .../eventdev_pipeline_queue_test_generic.svg | 570 +++++++-----
> ...dev_pipeline_queue_test_internal_port.svg} | 22 +-
Updated diagrams looks good.
Since this file gets modified, Can you add the missing pipeline tests in
--test <name> documentation.
With above change:
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2018-09-23 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 14:12 [dpdk-dev] [PATCH v2 1/4] app/test-eventdev: fix minor typos Pavan Nikhilesh
2018-09-04 14:12 ` [dpdk-dev] [PATCH v2 2/4] app/test-eventdev: remove redundant newlines Pavan Nikhilesh
2018-09-04 14:12 ` [dpdk-dev] [PATCH v2 3/4] app/test-eventdev: add Tx adapter support Pavan Nikhilesh
2018-09-05 6:54 ` Rao, Nikhil
2018-09-05 8:54 ` Pavan Nikhilesh
2018-09-05 9:37 ` Rao, Nikhil
2018-09-04 14:12 ` [dpdk-dev] [PATCH v2 4/4] doc: update eventdev application guide Pavan Nikhilesh
2018-09-19 22:22 ` [dpdk-dev] [PATCH v3 1/4] app/test-eventdev: fix minor typos Pavan Nikhilesh
2018-09-19 22:22 ` [dpdk-dev] [PATCH v3 2/4] app/test-eventdev: remove redundant newlines Pavan Nikhilesh
2018-09-23 10:31 ` Jerin Jacob
2018-09-19 22:22 ` [dpdk-dev] [PATCH v3 3/4] app/test-eventdev: add Tx adapter support Pavan Nikhilesh
2018-09-23 11:35 ` Jerin Jacob
2018-09-24 8:30 ` Andrzej Ostruszka
2018-09-24 14:45 ` Jerin Jacob
2018-09-19 22:22 ` [dpdk-dev] [PATCH v3 4/4] doc: update eventdev application guide Pavan Nikhilesh
2018-09-23 10:46 ` Jerin Jacob [this message]
2018-09-23 10:28 ` [dpdk-dev] [PATCH v3 1/4] app/test-eventdev: fix minor typos Jerin Jacob
2018-09-24 8:02 ` [dpdk-dev] [PATCH v4 " Pavan Nikhilesh
2018-09-24 8:02 ` [dpdk-dev] [PATCH v4 2/4] app/test-eventdev: remove redundant newlines Pavan Nikhilesh
2018-09-24 8:02 ` [dpdk-dev] [PATCH v4 3/4] app/test-eventdev: add Tx adapter support Pavan Nikhilesh
2018-09-28 16:13 ` Jerin Jacob
2018-09-24 8:02 ` [dpdk-dev] [PATCH v4 4/4] doc: update eventdev application guide Pavan Nikhilesh
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=20180923104636.GC20954@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=anoob.joseph@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nikhil.rao@intel.com \
--cc=pbhagavatula@caviumnetworks.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).