From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] qdisc's useless in my case?
Date: Wed, 11 Jan 2006 01:03:18 +0000 [thread overview]
Message-ID: <43C45956.2060600@dsl.pipex.com> (raw)
In-Reply-To: <op.s2536rj9uplg4a@x50.wh242.lan>
André Matuschek wrote:
> Now what I worry about ist if this has any effect at all. Maybe the
> kernel sends
> all the Packets from the LAN (from eth0) to the to cable-modems, which are
> connected via 100Mbit crossover-cable and the modem queues the packets
> itself
> and drops the ones exceeding the maximum upload rate. With an constant
> empty
> queue in the kernel it would make no differences if fifo_fast or sfq is
> the qdisc, right?
>
> So my question is: Am I right? Is it useless to assign sfq to eth1 &
> eth2? What would
> be an alternative solution?
Yes you are right. You need to use htb/hfsc/cbq on both eths and limit
the traffic headed for the internet to < each cable rate. You could use
sfq as part of the setup, it is better to try and seperate interactive
traffic from bulk and only use sfq on the bulk. You could also limit
inbound traffic by shaping on the lan facing eth (if it goes to both lan
eths then it's more complicated but possible).
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-11 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 15:05 [LARTC] qdisc's useless in my case? André Matuschek
2006-01-11 1:03 ` Andy Furniss [this message]
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=43C45956.2060600@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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 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.