Re: [PATCH net v2 1/1] net: batman-adv: Treat NET_XMIT_CN as transmit successfully

Hi Florian, On Mon, Nov 21, 2016 at 9:24 PM, Gao Feng wrote: > Hi Florian, > > On Mon, Nov 21, 2016 at 7:09 PM, Florian Westphal wrote: >> f...@ikuai8.com wrote: >>> From: Gao Feng >>> >>> The tc could return NET_XMIT_CN as one congestion notification, but >>> it does not mean the packet is l

Re: [PATCH net v2 1/1] net: batman-adv: Treat NET_XMIT_CN as transmit successfully

Hi Florian, On Mon, Nov 21, 2016 at 7:09 PM, Florian Westphal wrote: > f...@ikuai8.com wrote: >> From: Gao Feng >> >> The tc could return NET_XMIT_CN as one congestion notification, but >> it does not mean the packet is lost. Other modules like ipvlan, >> macvlan, and others treat NET_XMIT_CN a

Re: [PATCH net v2 1/1] net: batman-adv: Treat NET_XMIT_CN as transmit successfully

f...@ikuai8.com wrote: > From: Gao Feng > > The tc could return NET_XMIT_CN as one congestion notification, but > it does not mean the packet is lost. Other modules like ipvlan, > macvlan, and others treat NET_XMIT_CN as success too. > > So batman-adv should add the NET_XMIT_CN check. "The tc

[PATCH net v2 1/1] net: batman-adv: Treat NET_XMIT_CN as transmit successfully

From: Gao Feng The tc could return NET_XMIT_CN as one congestion notification, but it does not mean the packet is lost. Other modules like ipvlan, macvlan, and others treat NET_XMIT_CN as success too. So batman-adv should add the NET_XMIT_CN check. Signed-off-by: Gao Feng --- v2: Correct two