From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Jason Wang <jasowang@redhat.com>, dev@dpdk.org
Cc: stephen@networkplumber.org,
Bruce Richardson <bruce.richardson@intel.com>,
Tiwei Bie <tiwei.bie@intel.com>
Subject: Re: [dpdk-dev] [RFC] testpmd: handle UFO packets
Date: Wed, 28 Feb 2018 22:53:56 +0800 [thread overview]
Message-ID: <d10ebed6-46bf-aefa-b7bf-6aeb148abac1@intel.com> (raw)
In-Reply-To: <098ad68d-20af-7646-7be3-ea260333960b@redhat.com>
Hi Jason,
On 2/28/2018 10:10 PM, Jason Wang wrote:
>
>
> On 2018年02月24日 17:35, Jianfeng Tan wrote:
>> Mostly likely, we will make UFO as a kind of GSO engine.
>>
>> For short term, we can just call APIs in librte_ip_frag to fragment.
>>
>> To test:
>>
>> 1. start testpmd with two vhost port.
>> $ set fwd csum
>> $ start
>>
>> 2. start vm0 connected to vhost0;
>> $ ifconfig xxx 1.1.1.1/24 up
>> $ ethtool -K xxx ufo on
>>
>> 3. start vm1 connected to vhost1;
>> $ ifconfig xxx 1.1.1.2/24 up
>> $ ethtool -K xxx ufo on
>> $ (Fill a large file named 1.txt)
>> $ cat 1.txt | socat - udp-sendto:1.1.1.1:5000
>
> Just a reminder, UFO was completely removed upstream.
>
Thank you for the information.
Saw the deprecation patch at Linux v4.16-rc3, wonder what "version+"
counts "merden kernels" in "modern kernels will no longer generate UFO
skbs"? And this is mostly for stock VMs with old kernels to help the
migration from kernel vswitch to user space vswitch.
Will other OSes generate UFO packets, FreeBSD, Windows? Anyone can
provide such information?
Thanks,
Jianfeng
next prev parent reply other threads:[~2018-02-28 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 9:35 Jianfeng Tan
2018-02-28 14:10 ` Jason Wang
2018-02-28 14:53 ` Tan, Jianfeng [this message]
2018-03-01 8:36 ` Jason Wang
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=d10ebed6-46bf-aefa-b7bf-6aeb148abac1@intel.com \
--to=jianfeng.tan@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jasowang@redhat.com \
--cc=stephen@networkplumber.org \
--cc=tiwei.bie@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).