From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how tc deal with non-classified packets
Date: Tue, 22 May 2001 02:29:23 +0000 [thread overview]
Message-ID: <marc-lartc-99049862315942@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99049496809648@msgid-missing>
On Tue, May 22, 2001 at 09:23:42AM +0800, Daniel Lee wrote:
> Hi all,
>
> Does any one know how tc deal with non-classified packets?
> For example, I set up 10 classes with "bounded" and "isolated" rules to
> occupy the whole BW on my LAN and these classes are filtered by their ip dst
> add with u32. And then one long train of pkts which not belong to these 10
> classes enter tc router. Then, what will happen? tc will just drop it or
> consume others BW to send it.
>
> In my measurement, tc will occupy BW of the classified classes and send this
> "intruder". The experiment data does not seem to be reasonable!
>
> Any related information or experiment data is highly appreciated.
Very good question. As long as any entry of your routing tables match the
packetss they'll be routed out of the box, so will not be dropped. But,
we need a guru to explain which of the queues is used for these packets???
Ramin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-05-22 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 1:23 [LARTC] how tc deal with non-classified packets Daniel Lee
2001-05-22 2:29 ` Ramin Alidousti [this message]
2001-05-22 19:45 ` Wingtung.Leung
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-99049862315942@msgid-missing \
--to=ramin@uu.net \
--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.