From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "harry.van.haaren@intel.com" <harry.van.haaren@intel.com>,
"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info
Date: Fri, 8 Mar 2019 18:25:54 +0000 [thread overview]
Message-ID: <666330bcaf66637e43250bc28b40d091bfc00a8a.camel@marvell.com> (raw)
In-Reply-To: <20190301071617.6570-1-pbhagavatula@marvell.com>
On Fri, 2019-03-01 at 07:16 +0000, Pavan Nikhilesh Bhagavatula wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Some eventdevs support configuring max events to be -1 (open system).
> Check eventdev and event port configuration with eventdev info before
> configuring them.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> examples/eventdev_pipeline/pipeline_worker_generic.c | 6 ++++++
> examples/eventdev_pipeline/pipeline_worker_tx.c | 6 ++++++
Hi Harry,
Any comments on this patch series as examples/eventdev_pipeline
maintainer?
next prev parent reply other threads:[~2019-03-08 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 7:16 Pavan Nikhilesh Bhagavatula
2019-03-01 7:16 ` [dpdk-dev] [PATCH 2/3] examples/eventdev_pipeline: follow proper teardown sequence Pavan Nikhilesh Bhagavatula
2019-03-11 9:57 ` Van Haaren, Harry
2019-03-01 7:16 ` [dpdk-dev] [PATCH 3/3] app/eventdev: " Pavan Nikhilesh Bhagavatula
2019-03-11 9:58 ` Van Haaren, Harry
2019-03-11 15:12 ` Jerin Jacob Kollanukkaran
2019-03-08 18:25 ` Jerin Jacob Kollanukkaran [this message]
2019-03-11 9:57 ` [dpdk-dev] [PATCH 1/3] examples/eventdev_pipeline: configure max events based on dev info Van Haaren, Harry
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=666330bcaf66637e43250bc28b40d091bfc00a8a.camel@marvell.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=pbhagavatula@marvell.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).