From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Hardware Requirements for qdisc htb/sfq
Date: Wed, 14 Nov 2007 22:04:29 +0000 [thread overview]
Message-ID: <20071114230429.187dbd5d@catlap> (raw)
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BF42B1F@s-marcell.hemc.coop>
>So I should prolly be good with the hardware listed, huh? I am mostly
>concerned about the qdisc stuff, is it more CPU intensive or RAM?
Shaping is not RAM hogging at all. With simpler setups It should not be
too CPU intensive either. If you plan to do per-user shaping then
consider using hashing u32 filters.
cheers,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-11-14 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:44 [LARTC] Hardware Requirements for qdisc htb/sfq Shane McKinley
2007-11-14 21:36 ` Marek Kierdelewicz
2007-11-14 21:51 ` Shane McKinley
2007-11-14 22:04 ` Marek Kierdelewicz [this message]
2007-11-15 1:59 ` Mohan Sundaram
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=20071114230429.187dbd5d@catlap \
--to=marek@piasta.pl \
--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.