From: Johnray Fuller <jrfuller@redhat.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Quality of Service with VLAN using Traffic Control (tc)
Date: Thu, 18 Oct 2007 13:58:20 +0000 [thread overview]
Message-ID: <4717667C.2040607@redhat.com> (raw)
We are using VLAN tagging to put several networks on one machine.
To ensure quality of service on one of the VLANs, we would like to
prioritize (outgoing/egress traffic) one VLAN interface over the other
(or others), but without capping bandwidth on any of the interfaces.
We want to do this while being careful to minimize increases in
latency on the prioritized interface.
Since these are two or more separate VLAN interfaces on the same
physical NIC, we want to know if specific policies assigned to each
interface through the tc command would be best suited for this task. At
the moment we are using the classless prio_fifo qdisc parameter in
tc. Are there other qdisciplines we should consider (such as the
classful HTB). In other words, what tc policies have the best low
latency principles for the prioritized VLAN?
Also under consideration are IMQ meta-interfaces for system wide
traffic shaping across multiple interfaces. But does the use of IMQ and
the requisite iptables packet tagging have a siginificant impact on
increases latency in your experience?
Finally, is a weighted round-robin queuing algorithm supported. I was
unable to figure this out.
Thanks for any assistance you can provide.
Johnray
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-10-18 13:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4717667C.2040607@redhat.com \
--to=jrfuller@redhat.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.