From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: [Linux Diffserv] TC architecture made for Diffserv on linux is wrong !!! why?
Date: Fri, 29 Jun 2001 04:35:10 +0000 [thread overview]
Message-ID: <marc-lartc-99378938330463@msgid-missing> (raw)
jinho Hwang wrote:
> As this output's sch_dsmark has a FIFO queue, Best effort traffic
> and AF classes traffic is
> combined and does not guaranteed AF classes.
Hmm, so why don't you use CBQ/PRIO and maybe GRED then, i.e. something
that gives AF priority over BE ?
> To solve these demerits, I made ingress marker in linux kernel 2.4.x.
> that is, I take DSCP marking part 's position in input device part .
You don't have to mark in order to classify based on the DS field.
Just use skb->tc_index to convey that information. You can set
skb->tc_index at ingress or at egress (with dsmark).
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Lausanne, CH wa@almesberger.net /
/_http://icawww.epfl.ch/almesberger/_____________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-06-29 4:35 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=marc-lartc-99378938330463@msgid-missing \
--to=wa@almesberger.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.