From: Bill Gradwohl <bill@ycc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Duplexing
Date: Mon, 09 Aug 2004 14:13:41 +0000 [thread overview]
Message-ID: <41178695.20908@ycc.com> (raw)
The recent thread titled:
working ftp shaping, i think
provided a script example where 100Mbps was specified as the rate for a
typical NIC.
If that NIC is connected to a switch, chances are that it runs at
100Mbps in each direction concurrently - duplexed Writing a rule that
specifies a 100Mbps rate and thereby a 100Mbps ceil, limits the
connection to half the available bandwidth.
I haven't seen anything in tc (not iptables) that addresses direction -
inbound or outbound.
Is there a way of writing rules that take duplexing into account so that
you end up with 2 virtual devices, each capable of 100Mbps, but the
traffic is direction specific?
--
Bill Gradwohl
bill@ycc.com
http://www.ycc.com
SPAMstomper Protected email
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-08-09 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:13 Bill Gradwohl [this message]
2004-08-09 14:26 ` [LARTC] Duplexing Tomas Simonaitis
2004-08-09 14:38 ` David Boreham
2004-08-09 15:01 ` John Sullivan
2004-08-09 15:06 ` Rene Gallati
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=41178695.20908@ycc.com \
--to=bill@ycc.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.