netdev - Re: [PATCH 20/21] net: warn if drivers set tx_queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20150819210409.C5BF82137D@mail.nwl.cc>
Date:	Wed, 19 Aug 2015 23:04:43 +0200
From:	Phil Sutter <phil@....cc>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	netdev@...r.kernel.org, brouer@...hat.com, davem@...emloft.net
Subject: Re: [PATCH 20/21] net: warn if drivers set tx_queue_len = 0

On Wed, Aug 19, 2015 at 01:33:40PM -0700, Eric Dumazet wrote:
> On Wed, 2015-08-19 at 13:31 -0700, Eric Dumazet wrote:
> 
> > lpaa5:~# tc qd sh dev eth1
> > qdisc mq 0: root 
> > qdisc fq 0: parent :4 limit 10000p flow_limit 1000p buckets 1024 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 quantum 3028 initial_quantum 15140 
> > qdisc fq 0: parent :3 limit 10000p flow_limit 1000p buckets 1024 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 quantum 3028 initial_quantum 15140 
> > qdisc fq 0: parent :2 limit 10000p flow_limit 1000p buckets 1024 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 quantum 3028 initial_quantum 15140 
> > qdisc fq 0: parent :1 limit 10000p flow_limit 1000p buckets 1024 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 quantum 3028 initial_quantum 15140 
> 
> Well, it seems I just leaked fact that we use 3-bands in our fq
> implementation ;)

The problem with subtle details is they cease to be if pointed out. In
another episode I was about to ask who the ominous "we" are, but then I
noticed your mail's message ID. :)

Cheers, Phil
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html