All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burnside, Andrew" <Andrew.Burnside@thalesgroup.com>
To: lartc@vger.kernel.org
Subject: [LARTC] RE: LARTC digest, Vol 1 #1233 - 16 msgs
Date: Fri, 20 Jun 2003 08:14:06 +0000	[thread overview]
Message-ID: <marc-lartc-105609739413558@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105596167926461@msgid-missing>

cheers.
Having had another look at the kernel, and at the lartc howto it seems that
tc filter when policing may be able to reclassify out of profile traffic to
BE, but no more than this, without first putting traffic into a queue. 

Andrew

-----Original Message-----
From: Leonardo Balliache [mailto:leoball@opalsoft.net]
Sent: Wednesday, June 18, 2003 7:39 PM
To: Andrew.Burnside@thalesgroup.com
Cc: lartc@mailman.ds9a.nl
Subject: Re: LARTC digest, Vol 1 #1233 - 16 msgs


Andrew:

Differentiated Service on Linux HOWTO (work in progress) could be of some 
help for you.

Have a look at http://opalsoft.net/qos

Best regards,

Leonardo Balliache

>Message: 6
>From: "Burnside, Andrew" <Andrew.Burnside@thalesgroup.com>
>To: "'lartc@mailman.ds9a.nl'" <lartc@mailman.ds9a.nl>
>Date: Wed, 18 Jun 2003 13:24:44 +0100
>Subject: [LARTC] DiffServ Marking
>
>I am trying to compare the behaviour of the Linux DiffServ implementation
>with that of Cisco, in DSCP remarking for traffic policing.
>As I understand it, the DSCP is marked at the egress interface (parent
>queue), based on the class that packets are in.
>
>I am looking at what happens at an inter-AS boundary.
>DSCP marked traffic coming into the Edge Router need to be policed and
>remarked:
>e.g. EF traffic up to 2Mbps marked as EF
>EF traffic beyond 2Mbps should be policed and remarked as BE.
>Is there a way to do this remarking before the traffic is segregated into
>egress queues?
>
>Cheers
>
>Andrew


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2003-06-20  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 18:39 [LARTC] Re: LARTC digest, Vol 1 #1233 - 16 msgs Leonardo Balliache
2003-06-20  8:14 ` Burnside, Andrew [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-105609739413558@msgid-missing \
    --to=andrew.burnside@thalesgroup.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.