DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Vamsi Attunuru <vattunuru@marvell.com>
Cc: dev@dpdk.org, jerinj@marvell.com, sthotton@marvell.com
Subject: Re: [PATCH v6 3/3] net/octeon_ep: add new fastpath routines
Date: Thu, 19 Oct 2023 08:33:44 +0530	[thread overview]
Message-ID: <CALBAE1PkC9b1JaJ=tKBayJiqHa4btG0icXobxv-84HUYtNO=Bw@mail.gmail.com> (raw)
In-Reply-To: <20231018111404.686147-4-vattunuru@marvell.com>

On Thu, Oct 19, 2023 at 6:52 AM Vamsi Attunuru <vattunuru@marvell.com> wrote:
>
> Adds new fastpath routines for cn10k & cn9k endpoint
> devices and assigns the fastpath routines based on
> the offload flags.
>
> Patch also adds misc changes to improve performance
> and code-readability.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>

Series applied to dpdk-next-net-mrvl/for-next-net. Thanks

      reply	other threads:[~2023-10-19  3:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  1:50 [PATCH 0/3] rewrite " Vamsi Attunuru
2023-10-11  1:50 ` [PATCH 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-11  1:50 ` [PATCH 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-11  1:50 ` [PATCH 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-11  8:36 ` [PATCH v2 0/3] rewrite " Vamsi Attunuru
2023-10-11  8:36   ` [PATCH v2 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-11  8:36   ` [PATCH v2 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-11  8:36   ` [PATCH v2 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-11 12:53   ` [PATCH v3 0/3] rewrite " Vamsi Attunuru
2023-10-11 12:53     ` [PATCH v3 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-11 12:53     ` [PATCH v3 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-11 12:53     ` [PATCH v3 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-12  6:23     ` [PATCH v4 0/3] rewrite " Vamsi Attunuru
2023-10-12  6:23       ` [PATCH v4 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-12  6:23       ` [PATCH v4 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-12  6:23       ` [PATCH v4 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-18  3:48         ` Jerin Jacob
2023-10-18  8:07       ` [PATCH v5 0/3] rewrite " Vamsi Attunuru
2023-10-18  8:07         ` [PATCH v5 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-18  8:07         ` [PATCH v5 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-18  8:07         ` [PATCH v5 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-18 11:14         ` [PATCH v6 0/3] rewrite " Vamsi Attunuru
2023-10-18 11:14           ` [PATCH v6 1/3] net/octeon_ep: support 32B IQ descriptor size Vamsi Attunuru
2023-10-18 11:14           ` [PATCH v6 2/3] net/octeon_ep: clean up receive routine Vamsi Attunuru
2023-10-18 11:14           ` [PATCH v6 3/3] net/octeon_ep: add new fastpath routines Vamsi Attunuru
2023-10-19  3:03             ` 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='CALBAE1PkC9b1JaJ=tKBayJiqHa4btG0icXobxv-84HUYtNO=Bw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=sthotton@marvell.com \
    --cc=vattunuru@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).