Re: [BUG] moving fq back to clock monotonic breaks my setup

2019-01-11 Thread Ian Kumlien
On Fri, Jan 11, 2019 at 10:35 AM Eric Dumazet wrote: > On Thu, Jan 10, 2019 at 12:55 AM Paolo Abeni wrote: > > On Thu, 2019-01-10 at 09:25 +0100, Ian Kumlien wrote: > > > > > This works, and so does: > > > https://marc.info/?l=linux-netdev&m=154696956604748&w=2 > > > > > > Pointed out by Paolo (

Re: [BUG] moving fq back to clock monotonic breaks my setup

2019-01-11 Thread Eric Dumazet
On Thu, Jan 10, 2019 at 12:55 AM Paolo Abeni wrote: > > On Thu, 2019-01-10 at 09:25 +0100, Ian Kumlien wrote: > > This works, and so does: > > https://marc.info/?l=linux-netdev&m=154696956604748&w=2 > > > > Pointed out by Paolo (tested both separately) > > Note: I cleared the tstamp in br_forwa

Re: [BUG] moving fq back to clock monotonic breaks my setup

2019-01-10 Thread Paolo Abeni
On Thu, 2019-01-10 at 09:25 +0100, Ian Kumlien wrote: > On Thu, Jan 10, 2019 at 6:53 AM Eric Dumazet wrote: > > On Wed, Jan 9, 2019 at 4:48 PM Ian Kumlien wrote: > > > Hi, > > > > > > Just been trough ~5+ hours of bisecting and eventually actually found > > > the culprit =) > > > > > > commit f

Re: [BUG] moving fq back to clock monotonic breaks my setup

2019-01-10 Thread Ian Kumlien
On Thu, Jan 10, 2019 at 6:53 AM Eric Dumazet wrote: > On Wed, Jan 9, 2019 at 4:48 PM Ian Kumlien wrote: > > > > Hi, > > > > Just been trough ~5+ hours of bisecting and eventually actually found > > the culprit =) > > > > commit fb420d5d91c1274d5966917725e71f27ed092a85 (refs/bisect/bad) > > Author

Re: [BUG] moving fq back to clock monotonic breaks my setup

2019-01-09 Thread Eric Dumazet
On Wed, Jan 9, 2019 at 4:48 PM Ian Kumlien wrote: > > Hi, > > Just been trough ~5+ hours of bisecting and eventually actually found > the culprit =) > > commit fb420d5d91c1274d5966917725e71f27ed092a85 (refs/bisect/bad) > Author: Eric Dumazet > Date: Fri Sep 28 10:28:44 2018 -0700 > > tcp/fq

[BUG] moving fq back to clock monotonic breaks my setup

2019-01-09 Thread Ian Kumlien
Hi, Just been trough ~5+ hours of bisecting and eventually actually found the culprit =) commit fb420d5d91c1274d5966917725e71f27ed092a85 (refs/bisect/bad) Author: Eric Dumazet Date: Fri Sep 28 10:28:44 2018 -0700 tcp/fq: move back to CLOCK_MONOTONIC [--8<--] So this might be because my