From: Jerin Jacob <jerinjacobk@gmail.com>
To: Nithin Dabilpuram <ndabilpuram@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Vamsi Attunuru <vattunuru@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx2: add TSO offload support
Date: Fri, 4 Oct 2019 13:27:07 +0530 [thread overview]
Message-ID: <CALBAE1MwCa+chnnCdDGMiSkfSGn2mEj-EdOyCM7VUSJwFMvuxQ@mail.gmail.com> (raw)
In-Reply-To: <20190925045408.131578-2-ndabilpuram@marvell.com>
On Wed, Sep 25, 2019 at 10:28 AM Nithin Dabilpuram
<ndabilpuram@marvell.com> wrote:
>
> Add support to below TCP segmentation offloads for
> 96XX A1 onwards and 95xx B0 onwards.
> - TCPv4, TCPv6
> - VXLAN[v4 | v6][v4 | v6]
> - GENEVE[v4 | v6][v4 | v6]
>
> This patch also modifies a fastpath function to be forced
> inline due to performance reasons for multi-seg mode.
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> ---
>
Updated missing TSO support in doc/guides/nics/features/octeontx2_vf.ini.
Only in vector mode, TSO is not supported.
Applied to dpdk-next-net-mrvl/master. Thanks
next prev parent reply other threads:[~2019-10-04 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 4:54 [dpdk-dev] [PATCH] net/octeontx2: add GRE " Nithin Dabilpuram
2019-09-25 4:54 ` [dpdk-dev] [PATCH v2] net/octeontx2: add " Nithin Dabilpuram
2019-10-04 7:57 ` Jerin Jacob [this message]
2019-10-04 8:32 ` [dpdk-dev] [PATCH] net/octeontx2: add GRE " Jerin Jacob
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 8:53 [dpdk-dev] [PATCH] net/octeontx2: add " Nithin Dabilpuram
2019-09-25 4:36 ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
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=CALBAE1MwCa+chnnCdDGMiSkfSGn2mEj-EdOyCM7VUSJwFMvuxQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@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).