From: Thomas Monjalon <thomas@monjalon.net>
To: jerinj@marvell.com
Cc: web@dpdk.org, dev@dpdk.org, ferruh.yigit@intel.com,
dovrat@marvell.com, sburla@marvell.com, pathreya@marvell.com,
anoobj@marvell.com, irusskikh@marvell.com, pkapoor@marvell.com
Subject: Re: [dpdk-dev] [PATCH] update Marvell roadmap for 21.05
Date: Sun, 28 Feb 2021 18:29:32 +0100 [thread overview]
Message-ID: <9669036.m9tqWI0DDd@thomas> (raw)
In-Reply-To: <20210220084638.2924944-1-jerinj@marvell.com>
20/02/2021 09:46, jerinj@marvell.com:
> From: Jerin Jacob <jerinj@marvell.com>
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks.
> +- Introduce event vector support to reduce the scheduler overhead and to improve performance
> +- Add support for event vector support in SW Rx eventdev Adapter
> +- Update test-eventdev application to support event vector support
The last item is dropped because updating a test app is implicit
when adding a new feature.
prev parent reply other threads:[~2021-02-28 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 8:46 jerinj
2021-02-28 17:29 ` Thomas Monjalon [this message]
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=9669036.m9tqWI0DDd@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=ferruh.yigit@intel.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@marvell.com \
--cc=pathreya@marvell.com \
--cc=pkapoor@marvell.com \
--cc=sburla@marvell.com \
--cc=web@dpdk.org \
/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).