Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-21 Thread David Ahern
On 4/21/17 11:44 AM, Robert Shearman wrote: > > Can you send me some more details of your testing? It's a shell script that runs a long list of combinations of client, server and local traffic for ipv4 and ipv6 with addresses on the external interface, the vrf device and 127.0.0.1 on the VRF devi

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-21 Thread Robert Shearman
On 20/04/17 23:36, David Ahern wrote: On 4/10/17 8:21 AM, Robert Shearman wrote: Attempting to create a TCP socket not bound to a VRF device when a TCP socket bound to a VRF device with the same port exists (and vice versa) fails with EADDRINUSE. This limits the ability to use programs in select

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-20 Thread David Ahern
On 4/10/17 8:21 AM, Robert Shearman wrote: > Attempting to create a TCP socket not bound to a VRF device when a TCP > socket bound to a VRF device with the same port exists (and vice > versa) fails with EADDRINUSE. This limits the ability to use programs > in selected mixed VRF/non-VRF contexts. >

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-20 Thread David Ahern
On 4/20/17 7:01 AM, Robert Shearman wrote: >> The cached dst on sockets is one known place that causes a hang on a >> delete. Basically the delete stalls until the sockets are closed. I have >> a patch for sk_rx_dst which is the one I chased down last week. I got to the bottom on the sk_rx_dst cac

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-20 Thread Robert Shearman
On 13/04/17 15:36, David Ahern wrote: On 4/13/17 6:48 AM, Robert Shearman wrote: the patches look ok to me, but in testing them I see I refcnt problem. simple reproducer: ip li add red type vrf table 254 ip link set dev eth1 vrf red ip addr add 127.0.0.1/8 dev red ip link set dev eth1 up ip li

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-13 Thread David Ahern
On 4/13/17 6:48 AM, Robert Shearman wrote: >> the patches look ok to me, but in testing them I see I refcnt problem. >> simple reproducer: >> >> ip li add red type vrf table 254 >> ip link set dev eth1 vrf red >> ip addr add 127.0.0.1/8 dev red >> ip link set dev eth1 up >> ip li set red up >> ping

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-13 Thread Robert Shearman
On 12/04/17 17:51, David Ahern wrote: On 4/10/17 8:21 AM, Robert Shearman wrote: Attempting to create a TCP socket not bound to a VRF device when a TCP socket bound to a VRF device with the same port exists (and vice versa) fails with EADDRINUSE. This limits the ability to use programs in select

Re: [PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-12 Thread David Ahern
On 4/10/17 8:21 AM, Robert Shearman wrote: > Attempting to create a TCP socket not bound to a VRF device when a TCP > socket bound to a VRF device with the same port exists (and vice > versa) fails with EADDRINUSE. This limits the ability to use programs > in selected mixed VRF/non-VRF contexts. >

[PATCH net-next 0/3] l3mdev: Improve use with main table

2017-04-10 Thread Robert Shearman
Attempting to create a TCP socket not bound to a VRF device when a TCP socket bound to a VRF device with the same port exists (and vice versa) fails with EADDRINUSE. This limits the ability to use programs in selected mixed VRF/non-VRF contexts. This patch series solves the problem by extending th