From: Kiran KN <kirankn@juniper.net>
To: "Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
Subject: Re: [dpdk-dev] GSO/GRO support
Date: Mon, 13 Feb 2017 20:34:39 +0000 [thread overview]
Message-ID: <EFA38F36-7CD7-4D8B-BA15-2961B28200A4@juniper.net> (raw)
In-Reply-To: <ED946F0BEFE0A141B63BABBD629A2A9B3870B5EF@shsmsx102.ccr.corp.intel.com>
Hi All,
Glad to know that there is interest in this.
Currently the code as part of vrouter. But easily separable since its in separate files.
You can find the code for GRO here:
https://github.com/Juniper/contrail-vrouter/blob/master/dpdk/vr_dpdk_gro.c
GSO code is here:
https://github.com/Juniper/contrail-vrouter/blob/master/dpdk/vr_dpdk_gso.c
Will work on the RFC.
- Kiran
On 2/13/17, 5:58 AM, "Hu, Jiayu" <jiayu.hu@intel.com> wrote:
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kiran KN
>> Sent: Saturday, February 11, 2017 6:56 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] GSO/GRO support
>>
>> We, at Juniper Opencontrail have added software support for TCP send
>> offload and receive offload to DPDK.
>>
>> If the community is interested, we can publish/upstream it.
>>
>> Pl let us know what you think of it.
>>
>> Thanks,
>> Kiran
>
>Hi Kiran,
>
>I am glad to hear this news. And Currently, I work on the design of GRO and GSO too.
>After your codes or RFC is released, I am happy to join the discussion and do some
>reviews.
>
>Regards,
>Jiayu
prev parent reply other threads:[~2017-02-13 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 22:56 Kiran KN
2017-02-13 9:27 ` Kavanagh, Mark B
2017-02-13 10:31 ` Ananyev, Konstantin
2017-02-13 13:58 ` Hu, Jiayu
2017-02-13 20:34 ` Kiran KN [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=EFA38F36-7CD7-4D8B-BA15-2961B28200A4@juniper.net \
--to=kirankn@juniper.net \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mark.b.kavanagh@intel.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).