All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] MARK causes high CPU usage / using tc in conjunction
Date: Sun, 23 May 2004 22:30:57 +0000	[thread overview]
Message-ID: <40B12621.2010304@wildgooses.com> (raw)
In-Reply-To: <40AFC555.1010900@digis.net>


>Well, if you have 3000+ rules like that, it will certainly slow you down.
>You should use some kind of hashing. How that is done for tc filters,
>is described here: http://www.lartc.org/lartc.html#LARTC.ADV-FILTER.HASHING
>
>Apply the same (or a similar) mechanism to your iptables ruleset and 
>you should get improved speeds.
>  
>

If he wanted to keep the system of using iptables to classify and tc to 
filter, then couldn't he look at using seperate filter chains to 
decrease the search space?

Also, what about using return rules to speedup the search times in a 
given filter chain?

I think his point was actually that it was not a CPU issue without 
adding that one particular rule.  But perhaps you will have more success 
asking on the iptables list?

Good luck

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

  parent reply	other threads:[~2004-05-23 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 21:25 [LARTC] MARK causes high CPU usage / using tc in conjunction with MASQ Paul Lambert
2004-05-23 18:07 ` Andreas Klauer
2004-05-23 22:30 ` Ed Wildgoose [this message]
2004-05-23 23:27 ` Andreas Klauer
2004-05-24  0:50 ` [LARTC] MARK causes high CPU usage / using tc in conjunction Paul Lambert
2004-05-24 21:20 ` [LARTC] MARK causes high CPU usage / using tc in conjunction with MASQ miller69
2004-05-28 15:50 ` [LARTC] MARK causes high CPU usage / using tc in conjunction Paul Lambert

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=40B12621.2010304@wildgooses.com \
    --to=lists@wildgooses.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.