From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Sunil Kumar Kori <sunil.kori@nxp.com>, <jerin.jacob@caviumnetworks.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] event/dpaa: Support for eventdev
Date: Tue, 19 Dec 2017 16:58:18 +0530 [thread overview]
Message-ID: <817497f4-c91f-878f-b9f8-58bf5fd8b4af@nxp.com> (raw)
In-Reply-To: <20171215125933.14302-1-sunil.kori@nxp.com>
On 12/15/2017 6:29 PM, Sunil Kumar Kori wrote:
> Event device support for atomic and parallel queues.
>
> This patch set includes following changes:
> 1. Configuration of atomic and parallel queues with given event device.
> 2. Also maintains previous dequeue method, via poll mode queues.
> 3. Added Rx functions to dequeue data from portal.
> 4. DCA consumption logic for atomic queues.
> 5. Dynamic Logging macros for event device
>
Please also specify dependency on these patches if any on other patch
series.
next prev parent reply other threads:[~2017-12-19 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 12:59 Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 1/6] bus/dpaa: added event dequeue and consumption support Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 2/6] bus/dpaa: add dpaa eventdev dynamic log support Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 3/6] net/dpaa: ethdev Rx queue configurations with eventdev Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 4/6] event/dpaa: add eventdev PMD Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 5/6] config: enabling compilation of DPAA " Sunil Kumar Kori
2017-12-15 12:59 ` [dpdk-dev] [PATCH 6/6] doc: add DPAA eventdev guide Sunil Kumar Kori
2017-12-15 15:09 ` Kovacevic, Marko
2017-12-18 9:09 ` [dpdk-dev] [PATCH 0/6] event/dpaa: Support for eventdev Jerin Jacob
2017-12-19 11:28 ` Hemant Agrawal [this message]
2017-12-15 13:08 Sunil Kumar Kori
2017-12-16 12:31 ` Jerin Jacob
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=817497f4-c91f-878f-b9f8-58bf5fd8b4af@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=sunil.kori@nxp.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).