Re: Default qdisc not correctly initialized with custom MTU

2019-09-10 Thread Holger Hoffstätte
On 9/10/19 6:56 PM, Cong Wang wrote: It is _not_ created when sysctl is configured, it is either created via tc command, or implicitly created by kernel when you bring up eth0. sysctl only tells kernel what to create by default, but never commits it. Ok, thank you - that's good to know, because

Re: Default qdisc not correctly initialized with custom MTU

2019-09-10 Thread Cong Wang
On Tue, Sep 10, 2019 at 2:14 AM Holger Hoffstätte wrote: > > On 9/10/19 12:52 AM, Cong Wang wrote: > > On Mon, Sep 9, 2019 at 5:44 AM Holger Hoffstätte > > wrote: > >> I can't help but feel this is a slight bug in terms of initialization > >> order, > >> and that the default qdisc should only be

Re: Default qdisc not correctly initialized with custom MTU

2019-09-10 Thread Holger Hoffstätte
On 9/10/19 12:52 AM, Cong Wang wrote: On Mon, Sep 9, 2019 at 5:44 AM Holger Hoffstätte wrote: I can't help but feel this is a slight bug in terms of initialization order, and that the default qdisc should only be created when it's first being used/attached to a link, not when the sysctls are co

Re: Default qdisc not correctly initialized with custom MTU

2019-09-09 Thread Cong Wang
On Mon, Sep 9, 2019 at 5:44 AM Holger Hoffstätte wrote: > I can't help but feel this is a slight bug in terms of initialization order, > and that the default qdisc should only be created when it's first being > used/attached to a link, not when the sysctls are configured. Yeah, this is because th

Default qdisc not correctly initialized with custom MTU

2019-09-08 Thread Holger Hoffstätte
I just installed a better NIC (Aquantia 2.5/5/10Gb, apparently with multiple queues) and now get the "mq" pseudo-qdisc automatically installed - so far, so good. I also configure fq_codel as default qdisc via sysctls and a larger MTU of 9000 for the device. This somehow leads to some slight conf