Re: [PATCH net 1/1] net: l2tp: Treat NET_XMIT_CN as success in l2tp_eth_dev_xmit

2016-11-21 Thread Gao Feng
Hi Cong, On Tue, Nov 22, 2016 at 1:29 PM, Cong Wang wrote: > On Sun, Nov 20, 2016 at 4:56 PM, wrote: >> From: Gao Feng >> >> The tc could return NET_XMIT_CN as one congestion notification, but >> it does not mean the packe is lost. Other modules like ipvlan, >> macvlan, and others treat NET_XM

Re: [PATCH net 1/1] net: l2tp: Treat NET_XMIT_CN as success in l2tp_eth_dev_xmit

2016-11-21 Thread Cong Wang
On Sun, Nov 20, 2016 at 4:56 PM, wrote: > From: Gao Feng > > The tc could return NET_XMIT_CN as one congestion notification, but > it does not mean the packe is lost. Other modules like ipvlan, > macvlan, and others treat NET_XMIT_CN as success too. > So l2tp_eth_dev_xmit should add the NET_XMIT

Re: [PATCH net 1/1] net: l2tp: Treat NET_XMIT_CN as success in l2tp_eth_dev_xmit

2016-11-21 Thread David Miller
From: f...@ikuai8.com Date: Mon, 21 Nov 2016 08:56:21 +0800 > From: Gao Feng > > The tc could return NET_XMIT_CN as one congestion notification, but > it does not mean the packe is lost. Other modules like ipvlan, > macvlan, and others treat NET_XMIT_CN as success too. > So l2tp_eth_dev_xmit sho

[PATCH net 1/1] net: l2tp: Treat NET_XMIT_CN as success in l2tp_eth_dev_xmit

2016-11-20 Thread fgao
From: Gao Feng The tc could return NET_XMIT_CN as one congestion notification, but it does not mean the packe is lost. Other modules like ipvlan, macvlan, and others treat NET_XMIT_CN as success too. So l2tp_eth_dev_xmit should add the NET_XMIT_CN check. Signed-off-by: Gao Feng --- net/l2tp/l2