All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] packet marking: only a ratio, not all
Date: Fri, 07 Apr 2006 22:23:13 +0000	[thread overview]
Message-ID: <4436E651.7000705@dsl.pipex.com> (raw)

pfer wrote:
> Hi all!
>  
>  In short: 
>  
>  Anybody wrote a patch for DSMARK to make it capable of marking
>  only a ratio (a given arg to the tc command) of the packets it gets?
>  Say, 20%? Or, do I have to hack into the source? Alternatives,
>  like a filter spitting packets to 2 different DSMARK based on this ratio?
>  
>  In long:
>  
>  I'm a hungarian univ student involved in a project (RMD-QoS stuff)
>  which needs the following:
>  
>   \                    This node has 3 ingress and 1 egress link, all have for ex. 10 Mbit
>     \                  limit to their traffic.
>       \
>    ---  node -----  Suppose ingress traffic is: 8 + 3 +5 = 16 while the egress
>      /                 link will be congested with 10. Because this node is a simple,
>    /                   intradomain router, we would like to notify the downstream 
>  /                    edge node about this congestion, to tear down some of the flows
>                       causing it. (Congestion occured via for. ex. a net failure)
>  
>  What the protocol (draft) says, is that the edge will be notified of the level of the congestion, which will be calculated by this proportional data packet marking method, to avoid additional signaling.
>  Say, if 16 would go on a link with 10 capacity, congested core-node will mark
>  60% of the packets it sends to the output of the link to another DSCP.
>  
>  I thought about DSMARK first, but that is incapable of doing this stuff.
>  (or I think so :)
>  Ideas?
>  
>  PS: I did not check the archives rigorously, so sorry if I am asking trivial things.
>  
>  PS2: Since I checked not to get mails from this list, please send your answer
>  to forgamedev@yahoo.com.

I am not sure I get the logic of what you are trying to do for this 
paticular setup, but there are examples of using policers with meters 
shared across ingress links to dsmark overlimits packets in the iproute2 
sources.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-04-07 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 22:23 Andy Furniss [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-30 13:56 [LARTC] packet marking: only a ratio, not all pfer

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=4436E651.7000705@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.