Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: David McNab <david@rebirthing.co.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] Requesting Ingress Policing Examples
Date: Thu, 11 Mar 2004 13:32:32 +0000	[thread overview]
Message-ID: <40506A70.6020005@rebirthing.co.nz> (raw)

Hi,

I'm a complete newbie to tc, but have been learning enough to get a very 
basic grasp. (studying 'wondershaper', 'snitch' and other tc-using 
scripts has helped muchly).

My question relates to ingress policing.

I've got a basic understanding of setting up specific ingress policers, 
for example setting up one policer to limit HTTP download rates, and 
another to limit FTP download rates.

But from what I can gather, these limits are independent. For instance, 
if I set the HTTP download policer to a ceiling to 40kbit, and an FTP 
policer to a download ceiling to 20kbit, then concurrent HTTP and FTP 
downloads will total 60kbit.

  tc qdisc add DEV ingress handle ffff:
  tc filter add DEV parent ffff: protocol ip prio 50 u32 \
      match ip sport 80 0xffff \
      police rate 40kbit burst 10k drop flowid ffff:1
  tc filter add DEV parent ffff: protocol ip prio 50 u32 \
      match ip sport 21 0xffff \
      police rate 20kbit burst 10k drop flowid ffff:1

But what I'm wanting to do is set up a download pool of (say) 64kbit, 
and share that amongst n different filters.

I'm slowly gaining some clarity on how to do that via htb for outbound 
traffic, but is there any any way to set up shared pools for inbound?

I saw on the list archives some example using 'index nnn' as an 
argument, but the example was incomplete.

I've also scoured Google, but am not coming up with much.

Can anyone please point me to a rich set of working tc ingress policing 
examples, enough for me to build a general understanding?

Thanks muchly in advance

-- 

Kind regards
David

--

leave this line intact so your email gets through my junk mail filter
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2004-03-11 13:32 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=40506A70.6020005@rebirthing.co.nz \
    --to=david@rebirthing.co.nz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox