netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Patrick McHardy <kaber@trash.net>
Cc: hadi@cyberus.ca, qnex@atlantis.knm.org.pl, netdev@oss.sgi.com,
	shemminger@osdl.org
Subject: Re: 2.6: QoS scheduling not working with IP-over-IP
Date: Fri, 13 Feb 2004 21:36:06 -0800	[thread overview]
Message-ID: <20040213213606.5a13cc76.davem@redhat.com> (raw)
In-Reply-To: <402D54D6.5070708@trash.net>

On Fri, 13 Feb 2004 23:51:02 +0100
Patrick McHardy <kaber@trash.net> wrote:

> while looking for other devices that may be affected I noticed
> this fix changes behaviour in dev_activate. dev_activate creates
> pfifo_fast queues for devices with tx_queue_len != 0 and noqueue
> qdiscs otherwise.

Thanks for spotting this.

> Although it is uncomfortable for some users, I don't know if there
> is anything to fix at all. Work-conserving qdiscs are useless for
> virtual devices, as you say there is maximum one packet queued at
> any time. For non-work-conserving qdiscs with default pfifo qdiscs
> as leaves, I'd say it is simply a configuration error not to increase
> tx_queue_len. Even with a length of 1 (or a off-by-one), you won't get
> good results, except when the traffic is already well-formed. All that
> is changed is that nonsensical configurations stop working.

Another way to view this is that configurations that, while nonsensical,
used to send packets properly no longer do.

However, I do agree with you, and we should not promote this kind of crap.
I'm going to revert the changeset that set tx_queue_len to 1 in the tunnels.

Thanks again Patrick.

  parent reply	other threads:[~2004-02-14  5:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0402101324350.810-100000@atlantis.knm.org.pl>
2004-02-12  4:05 ` 2.6: QoS scheduling not working with IP-over-IP David S. Miller
2004-02-12  4:51   ` jamal
2004-02-12  4:59     ` jamal
2004-02-12  5:04       ` jamal
2004-02-12  5:15         ` David S. Miller
2004-02-12  5:25           ` jamal
2004-02-12  5:43             ` jamal
2004-02-12  5:51               ` David S. Miller
2004-02-12  6:09                 ` jamal
2004-02-12  6:22                   ` David S. Miller
     [not found]                     ` <402D54D6.5070708@trash.net>
2004-02-14  5:36                       ` David S. Miller [this message]
2004-02-14 12:45                         ` jamal
2004-02-14 13:06                           ` jamal
2004-02-14 13:56                             ` jamal
2004-02-14 20:49                               ` David S. Miller
2004-02-15 10:30                                 ` Patrick McHardy
2004-02-18  3:10                                   ` David S. Miller
2004-02-18 11:21                                     ` Patrick McHardy
2004-02-18 21:22                                       ` David S. Miller

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=20040213213606.5a13cc76.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=netdev@oss.sgi.com \
    --cc=qnex@atlantis.knm.org.pl \
    --cc=shemminger@osdl.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).