All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: tim.c.chen@linux.intel.com, linux-kernel@vger.kernel.org,
	davem@sunset.davemloft.net, kuznet@ms2.inr.ac.ru,
	netdev@vger.kernel.org
Subject: Re: 2.6.19-rc1: Volanomark slowdown
Date: Wed, 8 Nov 2006 17:29:55 +0100	[thread overview]
Message-ID: <20061108162955.GA4364@suse.de> (raw)
In-Reply-To: <1163001318.3138.346.camel@laptopd505.fenrus.org>

On Wed, Nov 08, 2006 at 04:55:18PM +0100, Arjan van de Ven wrote:
> I wonder if it's an option to use low priority QoS fields for these acks
> (heck I don't even know if ACKs have such fields in their packet) so
> that they can get dropped if there are more packets then there is
> bandwidth ....

Is it proven that the number of ACKs actually cause bandwidth problems?
I found Volanomark to exercise the scheduler more than anything else,
so maybe the slowdown, while triggered by an increased number of ACKs,
is caused by something else entirely.

Olaf
-- 
Walks like a duck. Quacks like a duck. Must be a chicken.

  reply	other threads:[~2006-11-08 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 18:32 2.6.19-rc1: Volanomark slowdown Tim Chen
2006-11-07 20:45 ` David Miller
2006-11-07 21:50   ` John Heffner
2006-11-07 22:22     ` David Miller
2006-11-07 22:29       ` John Heffner
2006-11-08 10:07   ` Alexey Kuznetsov
2006-11-08 15:55 ` Arjan van de Ven
2006-11-08 16:29   ` Olaf Kirch [this message]
2006-11-08 18:38     ` Tim Chen
2006-11-08 19:44       ` Arjan van de Ven
2006-11-08 22:10       ` Olaf Kirch
2006-11-08 22:07         ` Tim Chen
2006-11-08 23:00           ` Stephen Hemminger
2006-11-08 22:32             ` Tim Chen
2006-11-09  9:21           ` Olaf Kirch
2006-11-08 22:58         ` Stephen Hemminger
2006-11-09  1:08         ` Rick Jones

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=20061108162955.GA4364@suse.de \
    --to=okir@suse.de \
    --cc=arjan@infradead.org \
    --cc=davem@sunset.davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tim.c.chen@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.