From: Jason Wang <jasowang@redhat.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com,
Michal Kubecek <mkubecek@suse.cz>
Subject: Re: Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected
Date: Wed, 6 Dec 2017 11:08:41 +0800 [thread overview]
Message-ID: <a259bb30-8cc0-fceb-5481-1295de54b5fb@redhat.com> (raw)
In-Reply-To: <401a0715-fd28-63a3-8dfd-e89835d70db0@01019freenet.de>
On 2017年12月06日 00:23, Andreas Hartmann wrote:
> On 12/05/2017 at 04:50 AM Jason Wang wrote:
>>
>> On 2017年12月05日 00:28, Andreas Hartmann wrote:
>>> On 12/03/2017 at 12:35 PM Andreas Hartmann wrote:
>>>> On 12/01/2017 at 11:11 AM Andreas Hartmann wrote:
>>>>> Hello!
>>>>>
>>>>> I hopefully could get rid of both of my problems (hanging network w/
>>>>> virtio) and endless hanging qemu-process on VM shutdown by upgrading
>>>>> qemu from 2.6.2 to 2.10.1. I hope it will persist.
>>>> It didn't persist. 10h later - same problems happened again. It's just
>>>> much harder to trigger the problems.
>>>>
>>>> I'm now trying it with
>>>>
>>>> CONFIG_RCU_NOCB_CPU=y and
>>>> rcu_nocbs=0-15
>>>>
>>>> Since then, I didn't see any problem any more. But this doesn't mean
>>>> anything until now ... .
>>> Didn't work ether. Disabling vhost_net's zcopy hadn't any effect, too.
>>>
>>> => It's just finally broken since
>>>
>>> 2ddf71e23cc246e95af72a6deed67b4a50a7b81c
>>> net: add notifier hooks for devmap bpf map
>> Hi:
>>
>> Did you use XDP devmap in host? If not, please double check it was the
>> first bad commit since the patch should only work when XDP/devmap is
>> used on host.
> How do I know if XDP/devmap is enabled / used? Could you please give
> some hint?
>
>
> Thanks,
> Andreas
Something like:
./ip link | grep xdp
10: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 xdp qdisc mq master
kvmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
prog/xdp id 4 tag 0381911915bc8d7f
But you should have some recent version of ip.
Thanks
next prev parent reply other threads:[~2017-12-06 3:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 14:17 Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected Andreas Hartmann
2017-11-27 16:46 ` Andreas Hartmann
2017-11-27 16:55 ` Michal Kubecek
2017-11-27 19:09 ` Andreas Hartmann
2017-12-01 10:11 ` Andreas Hartmann
2017-12-03 11:35 ` Andreas Hartmann
2017-12-04 16:28 ` Andreas Hartmann
2017-12-05 3:50 ` Jason Wang
2017-12-05 16:23 ` Andreas Hartmann
2017-12-06 3:08 ` Jason Wang [this message]
2017-12-08 7:21 ` Andreas Hartmann
2017-12-08 8:47 ` Michal Kubecek
2017-12-08 10:31 ` Andreas Hartmann
2017-12-08 11:40 ` Michal Kubecek
2017-12-08 12:45 ` Andreas Hartmann
2017-12-08 12:58 ` Michal Kubecek
2017-12-08 13:13 ` Andreas Hartmann
2017-12-08 15:11 ` Jason Wang
2017-12-08 16:04 ` Willem de Bruijn
2017-12-08 20:11 ` Andreas Hartmann
2017-12-08 20:44 ` Andreas Hartmann
2017-12-11 15:54 ` Andreas Hartmann
2017-12-14 16:31 ` Andreas Hartmann
2017-12-14 22:17 ` Willem de Bruijn
2017-12-14 22:47 ` Willem de Bruijn
2017-12-15 6:05 ` Andreas Hartmann
2017-12-17 22:33 ` Willem de Bruijn
2017-12-18 17:11 ` Andreas Hartmann
2017-12-20 15:56 ` Andreas Hartmann
2017-12-20 22:44 ` Willem de Bruijn
2017-12-21 17:05 ` Andreas Hartmann
2017-12-21 17:11 ` Willem de Bruijn
2017-12-24 16:24 ` Andreas Hartmann
2017-12-24 18:54 ` Willem de Bruijn
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=a259bb30-8cc0-fceb-5481-1295de54b5fb@redhat.com \
--to=jasowang@redhat.com \
--cc=andihartmann@01019freenet.de \
--cc=john.fastabend@gmail.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
/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).