From: Jason Wang <jasowang@redhat.com>
To: Jianfeng Tan <jianfeng.tan@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] testpmd: handle UFO packets
Date: Wed, 28 Feb 2018 22:10:14 +0800 [thread overview]
Message-ID: <098ad68d-20af-7646-7be3-ea260333960b@redhat.com> (raw)
In-Reply-To: <1519464907-133452-1-git-send-email-jianfeng.tan@intel.com>
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.
Thanks
next prev parent reply other threads:[~2018-02-28 14:10 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 [this message]
2018-02-28 14:53 ` Tan, Jianfeng
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=098ad68d-20af-7646-7be3-ea260333960b@redhat.com \
--to=jasowang@redhat.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@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).