From: Jerin Jacob <jerinjacobk@gmail.com>
To: Harman Kalra <hkalra@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] event/octeontx: support new features
Date: Sun, 3 May 2020 20:08:17 +0530 [thread overview]
Message-ID: <CALBAE1Mvfhdrr44vxWgsMzki650=fnUheYNGJPOjmw1ZPcnxAw@mail.gmail.com> (raw)
In-Reply-To: <1588077612-15905-1-git-send-email-hkalra@marvell.com>
On Tue, Apr 28, 2020 at 6:11 PM Harman Kalra <hkalra@marvell.com> wrote:
>
> Since event-octeontx PMD and net-octeontx PMD works very
> tightly, so this patchset implements the event-octeontx
> side changes to support new features added to net-octeontx
> PMD.
Acked-by: Jerin Jacob <jerinj@marvell.com>
Series applied to dpdk-next-eventdev/master. Thanks.
>
> v2:
> * replace __hot with __rte_hot
>
> Harman Kalra (3):
> event/octeontx: add multi segment support to eventdev
> event/octeontx: add framework for Rx/Tx offloads
> event/octeontx: support Rx Tx checksum offload
>
> Vamsi Attunuru (1):
> event/octeontx: add VLAN filter offload support
>
> drivers/event/octeontx/ssovf_evdev.c | 24 +-
> drivers/event/octeontx/ssovf_evdev.h | 19 +-
> drivers/event/octeontx/ssovf_worker.c | 304 +++++++++++++++++++++-----
> drivers/event/octeontx/ssovf_worker.h | 125 ++++++++++-
> drivers/net/octeontx/octeontx_rxtx.h | 17 ++
> 5 files changed, 395 insertions(+), 94 deletions(-)
>
> --
> 2.18.0
>
prev parent reply other threads:[~2020-05-03 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:40 Harman Kalra
2020-04-28 12:40 ` [dpdk-dev] [PATCH v2 1/4] event/octeontx: add multi segment support to eventdev Harman Kalra
2020-04-28 12:40 ` [dpdk-dev] [PATCH v2 2/4] event/octeontx: add framework for Rx/Tx offloads Harman Kalra
2020-04-28 12:40 ` [dpdk-dev] [PATCH v2 3/4] event/octeontx: add VLAN filter offload support Harman Kalra
2020-04-28 12:40 ` [dpdk-dev] [PATCH v2 4/4] event/octeontx: support Rx Tx checksum offload Harman Kalra
2020-05-03 14:38 ` Jerin Jacob [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='CALBAE1Mvfhdrr44vxWgsMzki650=fnUheYNGJPOjmw1ZPcnxAw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jerinj@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).