From: "Björn Snippe" <bjoern@snippe.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ingress/egress shaping
Date: Mon, 27 Jan 2003 17:57:02 +0000 [thread overview]
Message-ID: <marc-lartc-104369031802182@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104368601427650@msgid-missing>
David Boreham wrote:
> Repeat: queueing is done on outbound interfaces.
Got it. :)
[...]
> I'd recommend that you setup a test machine with the tc
> stuff on it, and play around for a while. It's much easier
> to understand this stuff by performing experiments, using
> tcpdump , looking at the stats output from tc, and so on.
My 'test machine' is the up-and-running router for the dorm where I live
in :)
It's running fine, and all the basic stuff works like I think it should,
I just want to make sure I'm not wasting lots of performance by using a
silly configuration...
Thanks a lot for reassuring me,
Björn
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-27 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 16:45 [LARTC] ingress/egress shaping Björn Snippe
2003-01-27 17:20 ` Björn Snippe
2003-01-27 17:57 ` Björn Snippe [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=marc-lartc-104369031802182@msgid-missing \
--to=bjoern@snippe.de \
--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.