DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.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: Thu, 1 Mar 2018 16:36:30 +0800	[thread overview]
Message-ID: <f1ba1d67-53c8-5d81-6a4e-5e599ca7a438@redhat.com> (raw)
In-Reply-To: <d10ebed6-46bf-aefa-b7bf-6aeb148abac1@intel.com>



On 2018年02月28日 22:53, Tan, Jianfeng wrote:
> 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"? 

git describe d9d30adf56777c402c0027c0e6ae21f17cc0a365
v4.12-11055-gd9d30ad

So I think any Linux version beyond 4.12 won't generate any UFO packets.

> And this is mostly for stock VMs with old kernels to help the 
> migration from kernel vswitch to user space vswitch.
>

Yes, testpmd may still see UFO packets for old kernels. Just a reminder 
in case you miss it.

(Btw, we plan to support UDP tunnel offload for virtio-net.)

> Will other OSes generate UFO packets, FreeBSD, Windows? Anyone can 
> provide such information?

I don't know about them.

Thanks.

>
> Thanks,
> Jianfeng
>
>

      reply	other threads:[~2018-03-01  8:36 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
2018-03-01  8:36     ` Jason Wang [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=f1ba1d67-53c8-5d81-6a4e-5e599ca7a438@redhat.com \
    --to=jasowang@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.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).