From: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
To: Kiran KN <kirankn@juniper.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] GSO/GRO support
Date: Mon, 13 Feb 2017 09:27:37 +0000 [thread overview]
Message-ID: <DC5AD7FA266D86499789B1BCAEC715F85C7A9535@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <883E9C99-AC63-4A03-8B81-0E6DFDA7F173@juniper.net>
>
>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.
Hi Kiran,
I'd be very interested in this, with a view to integrating your APIs into Open vSwitch as a software fallback option for situations in which a particular NIC doesn't support TSO/LRO.
If/when you release the code I'd be happy to review and/or test it.
Thanks in advance,
Mark
>
>Thanks,
> Kiran
next prev parent reply other threads:[~2017-02-13 9:27 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 [this message]
2017-02-13 10:31 ` Ananyev, Konstantin
2017-02-13 13:58 ` Hu, Jiayu
2017-02-13 20:34 ` Kiran KN
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=DC5AD7FA266D86499789B1BCAEC715F85C7A9535@irsmsx105.ger.corp.intel.com \
--to=mark.b.kavanagh@intel.com \
--cc=dev@dpdk.org \
--cc=kirankn@juniper.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).