netdev - Re: NET_SCHED cbq dropping too many packets on a bonding interface

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080516072254.GC3992@ff.dom.local>
Date:	Fri, 16 May 2008 07:22:54 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Kingsley Foreman <kingsley@...ernode.com.au>
Cc:	Patrick McHardy <kaber@...sh.net>,
	Eric Dumazet <dada1@...mosbay.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: NET_SCHED cbq dropping too many packets on a bonding interface

On Fri, May 16, 2008 at 07:01:02AM +0000, Jarek Poplawski wrote:
> On Fri, May 16, 2008 at 03:42:18PM +0930, Kingsley Foreman wrote:
> ...
> > ok after some playing a bit if i use
> >
> > tc qdisc change dev bond0 parent 1: pfifo limit 30
> >
> > the dropped packets go away, im not sure if that is considered normal or  
> > not, however any number under 30 gives me issues.
> 
> If there are no significant differences in configs between these 2.6.22
> and 2.6.24/25 (e.g. things mentionned earlier by Eric) IMHO it's "more
> than normal", but as I've written it would need a lot of your time and
> work to check the rason.

BTW, it still doesn't have to mean any error: e.g. it could happen when
kernel throughput is better while NIC tx speed stayed the same. So, it
shouldn't probably bother you too much until there is no visible impact
on latency or rates.

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