Currently, openvswitch tries to disable LRO from the user space. This does
not work correctly when the device added is a vlan interface, though.
Instead of dealing with possibly complex stacked cross name space relations
in the user space, do the same as bridging does and call dev_disable_lro in
the kernel.

Signed-off-by: Jiri Benc <jbenc@redhat.com>
Acked-by: Flavio Leitner <fbl@redhat.com>
Acked-by: Pravin B Shelar <pshelar@nicira.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Jiri Benc 2015-06-02 14:36:34 +02:00 коммит произвёл David S. Miller
Родитель 88aeca15d6
Коммит 640b2b107c
1 изменённых файлов: 1 добавлений и 0 удалений

Просмотреть файл

@ -125,6 +125,7 @@ static struct vport *netdev_create(const struct vport_parms *parms)
if (err) if (err)
goto error_master_upper_dev_unlink; goto error_master_upper_dev_unlink;
dev_disable_lro(netdev_vport->dev);
dev_set_promiscuity(netdev_vport->dev, 1); dev_set_promiscuity(netdev_vport->dev, 1);
netdev_vport->dev->priv_flags |= IFF_OVS_DATAPATH; netdev_vport->dev->priv_flags |= IFF_OVS_DATAPATH;
rtnl_unlock(); rtnl_unlock();