netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: David Miller <davem@davemloft.net>, willemdebruijn.kernel@gmail.com
Cc: mkubecek@suse.cz, netdev@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Vlad Yasevic <vyasevic@redhat.com>
Subject: Re: regression: UFO removal breaks kvm live migration
Date: Wed, 8 Nov 2017 16:49:57 +0900	[thread overview]
Message-ID: <dc9af6e2-a886-3fc6-8f34-70d87a7a0d01@redhat.com> (raw)
In-Reply-To: <20171108.152624.282888162096095926.davem@davemloft.net>



On 2017年11月08日 15:26, David Miller wrote:
> From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
> Date: Wed, 8 Nov 2017 12:36:26 +0900
>
>> On Tue, Nov 7, 2017 at 5:02 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
>>> I didn't have time to think it through yet but perhaps we could allow
>>> setting TUN_F_UFO and ignore its value.
>> If the feature is enabled guests may try to send UFO packets, which
>> the host is no longer able to fragment.
>>
>> virtio_net_hdr_to_skb will drop the packets immediately based on
>> gso_type and tun_get_user will return EINVAL.
>>
>> Still, perhaps that's preferable as migration will succeed and most
>> guests won't ever try to send those packets in the first place.
> However, this would create the situation where there is no way
> to properly probe for the actual presence of UFO support.

I think we should not have any assumption on how guest will use the 
feature. So I could not come a better than bring it back partially for 
TAP, looks like we only need segment them in tun_get_user().

Thanks

  reply	other threads:[~2017-11-08  7:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  8:02 regression: UFO removal breaks kvm live migration Michal Kubecek
2017-11-08  3:36 ` Willem de Bruijn
2017-11-08  6:26   ` David Miller
2017-11-08  7:49     ` Jason Wang [this message]
2017-11-08  8:08       ` Willem de Bruijn
2017-11-08  8:25         ` Jason Wang
2017-11-08 11:32           ` David Miller
2017-11-08 12:53             ` Jason Wang
2017-11-08 12:58               ` David Miller
2017-11-10  5:32               ` Willem de Bruijn
2017-11-10  5:59                 ` David Miller
2017-11-17 14:31                 ` Willem de Bruijn
2017-11-17 14:48                   ` Willem de Bruijn
2017-11-17 23:00                     ` Willem de Bruijn
2017-11-08 16:01             ` Michael S. Tsirkin

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=dc9af6e2-a886-3fc6-8f34-70d87a7a0d01@redhat.com \
    --to=jasowang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=mkubecek@suse.cz \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.com \
    --cc=willemdebruijn.kernel@gmail.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).