From: Henrik Nordstrom <hno@marasystems.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages
Date: Mon, 10 Dec 2001 08:41:59 +0000 [thread overview]
Message-ID: <marc-lartc-100797848104503@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100785524509147@msgid-missing>
On Sunday 09 December 2001 22.41, jamal wrote:
> Look at the definition of work vs non-work conserving; This is design
> intent. If you look at the datapath, it is totaly meaningless to put
> queues at ingress, for routing when they are being queued on ingress as
> well.
(on egress as well I assume...)
True, but not all applications of shaping have the luxury of egress. For
example, consider the not too uncommon example of a computer connected via
100Mbps networking to a DSL modem, and you want to tune the use of the link
without needing to introduce a router inbetween.
> The implementation/extension is trivial. There is no need for it; I went
> at great lengths with Martin/devik on this Maybe he can help me here ;->
So do you have any argument why one should not be able to shape incoming
local traffic to a station in a good manner without having a router do the
shaping?
hh
Regards
Henrik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-10 8:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 20:43 [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages jamal
2001-12-08 21:30 ` bert hubert
2001-12-08 21:56 ` jamal
2001-12-08 23:08 ` bert hubert
2001-12-08 23:29 ` jamal
2001-12-08 23:30 ` jamal
2001-12-08 23:45 ` Henrik Nordstrom
2001-12-08 23:54 ` bert hubert
2001-12-09 1:19 ` jamal
2001-12-09 1:35 ` bert hubert
2001-12-09 2:11 ` jamal
2001-12-09 2:30 ` jamal
2001-12-09 11:38 ` Henrik Nordstrom
2001-12-09 14:40 ` bert hubert
2001-12-09 14:49 ` jamal
2001-12-09 15:01 ` jamal
2001-12-09 15:49 ` Henrik Nordstrom
2001-12-09 16:45 ` Henrik Nordstrom
2001-12-09 21:41 ` jamal
2001-12-09 22:33 ` Michael T. Babcock
2001-12-09 22:36 ` Michael T. Babcock
2001-12-10 1:12 ` Cédric Rivard
2001-12-10 7:53 ` Don Cohen
2001-12-10 8:38 ` Martin Devera
2001-12-10 8:41 ` Henrik Nordstrom [this message]
2001-12-10 9:59 ` Henrik Nordstrom
2001-12-10 11:35 ` Martin Devera
2001-12-10 11:59 ` Martin Devera
2001-12-10 12:00 ` Henrik Nordstrom
2001-12-10 12:14 ` bert hubert
2001-12-10 12:25 ` Henrik Nordstrom
2001-12-10 12:52 ` Martin Devera
2001-12-10 13:29 ` jamal
2001-12-10 13:40 ` Martin Devera
2001-12-10 13:42 ` Jim Fleming
2001-12-10 13:52 ` Michael T. Babcock
2001-12-10 13:54 ` Michael T. Babcock
2001-12-10 13:56 ` Gerry Creager N5JXS
2001-12-10 13:58 ` Michael T. Babcock
2001-12-10 14:02 ` Martin Devera
2001-12-10 14:51 ` Jim Fleming
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=marc-lartc-100797848104503@msgid-missing \
--to=hno@marasystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox