From: "David S. Miller" <davem@redhat.com>
To: Dawid Kuroczko <qnex@atlantis.knm.org.pl>
Cc: netdev@oss.sgi.com, shemminger@osdl.org
Subject: Re: 2.6: QoS scheduling not working with IP-over-IP
Date: Wed, 11 Feb 2004 20:05:49 -0800 [thread overview]
Message-ID: <20040211200549.736fa8b3.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402101324350.810-100000@atlantis.knm.org.pl>
[ moving from linux-kernel to correct mailing list... ]
Czesc Dawid,
On Tue, 10 Feb 2004 13:36:32 +0100 (CET)
Dawid Kuroczko <qnex@atlantis.knm.org.pl> wrote:
> There seems to be a bug in QoS scheduling code related to IP-over-IP
> tunnels (ipip.ko). My setup is a bit unusual -- my default route
> goes through tunl1, so I want it shaped. It worked fine with 2.4,
> but it doesn't with 2.6 (2.6.1 and 2.6.2, I made a transition quite
> recently).
Can you assign QoS schedulers and classifiers successfully to eth0
or some other non ipip device?
Does it work with 'tunl0' instead of 'tunl1'?
Stephen, I bet this problem got introduced when we moved ipip.c over
to dynamic netdevice allocation, can you take a look?
next prev parent reply other threads:[~2004-02-12 4:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 12:36 2.6: QoS scheduling not working with IP-over-IP Dawid Kuroczko
2004-02-12 4:05 ` David S. Miller [this message]
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
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=20040211200549.736fa8b3.davem@redhat.com \
--to=davem@redhat.com \
--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 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.