netdev - Re: bond + tc regression ?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090506104808.GA6115@ff.dom.local>
Date:	Wed, 6 May 2009 10:48:08 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Vladimir Ivashchenko <hazard@...ncoudi.com>
Cc:	Eric Dumazet <dada1@...mosbay.com>, netdev@...r.kernel.org
Subject: Re: bond + tc regression ?

On Wed, May 06, 2009 at 01:36:16PM +0300, Vladimir Ivashchenko wrote:
> On Wed, May 06, 2009 at 06:10:10AM +0000, Jarek Poplawski wrote:
> 
> > >> ifconfig -a
> > > 
> > > bond0     Link encap:Ethernet  HWaddr 00:1B:24:BD:E9:CC
> > >           inet addr:xxx.xxx.135.44  Bcast:xxx.xxx.135.47  Mask:255.255.255.248
> > >           inet6 addr: fe80::21b:24ff:febd:e9cc/64 Scope:Link
> > >           UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
> > >           RX packets:436076190 errors:0 dropped:391250 overruns:0 frame:0
> > >           TX packets:2620156321 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:4210046233 (3.9 GiB)  TX bytes:2520272242 (2.3 GiB)
> > 
> > Could you try e.g.: ifconfig bond0 txqueuelen 1000
> > before tc qdisc add?
> 
> The drops on ifconfig are not increasing - these numbers are there from some tests made
> before.
> 

I'm not sure what do you mean? IMHO you don't use qdiscs properly,
so any TX problems end with drops. (Older kernel versions could mask
this problem with requeuing.)

Jarek P.
--
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