All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: packet marking: only a ratio, not all
Date: Thu, 13 Apr 2006 00:36:21 +0000	[thread overview]
Message-ID: <443D9D05.6050203@dsl.pipex.com> (raw)
In-Reply-To: <20060410134848.17949.qmail@web54305.mail.yahoo.com>

pfer wrote:
> Hello!
> 
> Well I won't go into protocol details, but
> I do not care if an intra-domain node will be
> congested via packets on ingress. I will drop them,
> but check with "tc .. show .." how much I get on
> byte-level. Based on this, and maximum egress
> transmission rate of this congested node, I calculate
> Overload%, and remark leaving packets at that ratio.

OK I guess you know what you want - just thinking there wouldn't be much 
overload% if tcp was about and you were dropping.

> 
> Anyway this setup will serve as a demo, having
> reservations thoughout the domain for UDP video packet
> streams only.
> 
> I wrote to netdev-linux mailing list about how to hack
> in the sources of tc something like:
> 
> for every packet
>     if(rand()<(percent/100))
>          do_action
> 
> ,where rand() gives a float of 0..1

If that's userspace tc it may be OK - no floats in kernel code AFAIK.


> 
> Could you point me to someone who will probably help
> me with this?

I think netdev is the right place.

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

      parent reply	other threads:[~2006-04-13  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 13:48 [LARTC] RE: packet marking: only a ratio, not all pfer
2006-04-12 13:52 ` [LARTC] " Andy Furniss
2006-04-12 16:39 ` pfer
2006-04-13  0:36 ` Andy Furniss [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=443D9D05.6050203@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.