Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Memory Loading
Date: Mon, 19 Apr 2004 18:56:49 +0000	[thread overview]
Message-ID: <408420F1.4070002@rocksteady.com> (raw)
In-Reply-To: <4083F99C.9050304@rocksteady.com>

Thanks for your response.

Unfortunately, I *am* concerned about memory load, and I need to track 
down this information. The approximate numbers you suggested seem 
reasonable, but I need the precise answers. I don't use SFQ at all.

Roy wrote:
> You should not be concerned about memory load, it does not cost that much
> cpu load will be more noticeable bottleneck for your system in any way.
> 
> as about memeory i suppose it takes about 50-100bytes each rule and up to
> 100 kbytes each queue like sfq.
> 
> 
> ----- Original Message ----- 
> From: "Patrick Turley" <pturley@rocksteady.com>
> To: <lartc@mailman.ds9a.nl>
> Sent: Monday, April 19, 2004 7:09 PM
> Subject: [LARTC] Memory Loading
> 
> 
> 
>>Our system has potentially a few thousand firewall rules and
>>HTB
>>classes. I need to find out the amount of memory these things consume:
>>
>>     - iptables firewall rules
>>     - HTB classes
>>
>>If anyone has any easy links to this information, that would be great.
>>Failing that, a pointer to a good place to look in the source code would
>>be very helpful.
>>_______________________________________________
>>LARTC mailing list / LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>>
> 
> 
> 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-04-19 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 16:09 [LARTC] Memory Loading Patrick Turley
2004-04-19 18:53 ` Roy
2004-04-19 18:56 ` Patrick Turley [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=408420F1.4070002@rocksteady.com \
    --to=pturley@rocksteady.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox