From: "lihao" <lihao@mx.cei.gov.cn>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can Tc control incoming bandwidth?
Date: Wed, 16 May 2001 01:05:10 +0000 [thread overview]
Message-ID: <marc-lartc-98997510016386@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98991888717115@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
my mean is tc can control downstream?
lihao
----- Original Message -----
From: shen jing
To: lihao
Cc: lartc@mailman.ds9a.nl
Sent: Tuesday, May 15, 2001 6:05 PM
Subject: Re: [LARTC] Can Tc control incoming bandwidth?
As I know it's no way to do it by tc.
But perhaps that can be done by RSVP implemented in linux by
signalling.
James Shen
Hello all: i have viewed some mail, i have read adv route howto,i know tc can control incoming bandwidth fromhowto,but i know tc can't control incoming bandwidth from maillist.so i want to know,can tc controlincoming bandwidth? lihao
[-- Attachment #2: Type: text/html, Size: 2013 bytes --]
prev parent reply other threads:[~2001-05-16 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 9:27 [LARTC] Can Tc control incoming bandwidth? lihao
2001-05-15 10:05 ` shen jing
2001-05-16 1:05 ` lihao [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-98997510016386@msgid-missing \
--to=lihao@mx.cei.gov.cn \
--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.