From: Peter Surda <shurdeek@routehat.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wrr question
Date: Tue, 07 Jun 2005 21:46:33 +0000 [thread overview]
Message-ID: <20055723463311003@mail.routehat.org> (raw)
In-Reply-To: <fad9d48405060712357e1655aa@mail.gmail.com>
On Tue, 7 Jun 2005 23:33:20 +0200 Kenneth Kalmer <kenneth.kalmer@gmail.com>
wrote:
>Anycase, I just thought that WRR might offer a smoother experience for
>the users, but I'll stick with my HTB setup for now since it's working
>beautifully. If anybody has an alternative suggestion, please shout.
In case you pay by the amount of transferred data, WRR is probably not the right
choice.
Yours sincerely,
Peter
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-07 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 19:35 [LARTC] wrr question Kenneth Kalmer
2005-06-07 19:41 ` Peter Surda
2005-06-07 21:24 ` Jonathan Day
2005-06-07 21:33 ` Kenneth Kalmer
2005-06-07 21:46 ` Peter Surda [this message]
2005-06-08 20:01 ` Kenneth Kalmer
2005-06-08 20:23 ` Peter Surda
2005-06-09 11:15 ` Kenneth Kalmer
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=20055723463311003@mail.routehat.org \
--to=shurdeek@routehat.org \
--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.