netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Kingsley Foreman <kingsley@internode.com.au>
Cc: Patrick McHardy <kaber@trash.net>,
	Eric Dumazet <dada1@cosmosbay.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NET_SCHED cbq dropping too many packets on a bonding interface
Date: Fri, 16 May 2008 07:22:54 +0000	[thread overview]
Message-ID: <20080516072254.GC3992@ff.dom.local> (raw)
In-Reply-To: <20080516070102.GB3992@ff.dom.local>

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.

  reply	other threads:[~2008-05-16  7:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B28DA1911F61434C804723B7EE8A5C67@uglypunk>
2008-05-15  3:56 ` NET_SCHED cbq dropping too many packets on a bonding interface Andrew Morton
2008-05-15  5:21   ` Eric Dumazet
2008-05-15  6:16     ` Kingsley Foreman
2008-05-15  9:12       ` Jarek Poplawski
2008-05-15 10:06         ` Kingsley Foreman
2008-05-15 10:29           ` Jarek Poplawski
2008-05-15 15:59           ` Patrick McHardy
2008-05-15 16:09           ` Patrick McHardy
2008-05-15 18:09             ` Jarek Poplawski
2008-05-15 18:14               ` Patrick McHardy
2008-05-15 18:25             ` Jarek Poplawski
2008-05-15 18:32               ` Patrick McHardy
2008-05-15 18:46                 ` Jarek Poplawski
2008-05-15 21:27                   ` Kingsley Foreman
2008-05-16  5:49                     ` Jarek Poplawski
2008-05-16  6:12                       ` Kingsley Foreman
2008-05-16  7:01                         ` Jarek Poplawski
2008-05-16  7:22                           ` Jarek Poplawski [this message]
2008-05-16 11:56                             ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080516072254.GC3992@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dada1@cosmosbay.com \
    --cc=kaber@trash.net \
    --cc=kingsley@internode.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).