From: Ophir Munk <ophirmu@mellanox.com>
To: "Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Mark Kavanagh" <mark.b.kavanagh@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-dev] TCP GSO support above IPv6
Date: Mon, 23 Apr 2018 23:12:39 +0000 [thread overview]
Message-ID: <HE1PR0501MB231490427DAEDE9957855246D1890@HE1PR0501MB2314.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <ED946F0BEFE0A141B63BABBD629A2A9B388B3CAC@shsmsx102.ccr.corp.intel.com>
Hi,
Please see inline
> -----Original Message-----
> From: Hu, Jiayu [mailto:jiayu.hu@intel.com]
> Sent: Monday, April 23, 2018 4:07 AM
> To: Ophir Munk <ophirmu@mellanox.com>; dev@dpdk.org; Mark Kavanagh
> <mark.b.kavanagh@intel.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> <olgas@mellanox.com>
> Subject: RE: TCP GSO support above IPv6
>
> Hi Ophir,
>
> Comparing with IPv6, IPv4 is used more widely used and more popular.
> Therefore, when proposed the GSO library, we just planned to support IPv4.
>
> Do you have any usage scenarios that depend on IPv6?
The same usage scenarios with IPv4 may be applicable to IPv6 since the
application requesting TSO at layer 4 may not care about which IP is used at layer 3.
>
> Thanks,
> Jiayu
> > -----Original Message-----
> > From: Ophir Munk [mailto:ophirmu@mellanox.com]
> > Sent: Sunday, April 22, 2018 10:45 PM
> > To: dev@dpdk.org; Hu, Jiayu <jiayu.hu@intel.com>; Mark Kavanagh
> > <mark.b.kavanagh@intel.com>
> > Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> > <olgas@mellanox.com>
> > Subject: TCP GSO support above IPv6
> >
> > Hello Jiayu,
> > I wonder why librte_gso only supports TCP GSO above IPv4.
> > Can you please explain why TCP GSO is not supported above IPv6?
> > Are there plans to support it?
> >
> > Regards,
> > Ophir
next prev parent reply other threads:[~2018-04-23 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 14:45 Ophir Munk
2018-04-23 1:06 ` Hu, Jiayu
2018-04-23 23:12 ` Ophir Munk [this message]
2018-04-25 2:07 ` Hu, Jiayu
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=HE1PR0501MB231490427DAEDE9957855246D1890@HE1PR0501MB2314.eurprd05.prod.outlook.com \
--to=ophirmu@mellanox.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=mark.b.kavanagh@intel.com \
--cc=olgas@mellanox.com \
--cc=thomas@monjalon.net \
/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).