From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] imq config
Date: Thu, 09 Sep 2004 16:54:56 +0000 [thread overview]
Message-ID: <41408AE0.30608@pobox.com> (raw)
In-Reply-To: <1094703984.1492.7.camel@joel.d2visp.com>
Hi Joel, you didn't told us details about your scenario or special needs
but to me you don't look like a candidate for IMQ. It is ment to be
used when you need to set global defaults or when you need to use egress
filter features on ingress traffic.
Based in your message I supose that a qdisc of 100Kbps and child qdiscs
of 50 or 60Kbps would do what you need. This way it will restrict
traffic to 100Kbps and child classes will borrow from each other when
possible, but never higher then their parent.
Hope it helps...
Andre
Joel n.solanki wrote:
> Dear all,
>
> I know this is not imq mailing list. But many of the users over here
> have done exactly what i want.
>
> Requirement:- I want to tight bound eth1 for 100 kbps
> but after i want to create many classes of 64 kbps or 50 kbps and
> others. But the total sum of classes is more than 100 kbps so my eth1 is
> not restrciting total bandwidth at 100kbps.
>
> According to search on google imq is the solution.
>
> So any body over here have done this type of configuration.
> if any plz give me some little examples.
>
> I have already patched and compiled the imq and kernel.
> Now need to configure imq.
>
> Any help ???
>
> Regards,
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-09-09 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 4:38 [LARTC] imq config Joel n.solanki
2004-09-09 16:54 ` Andre Correa [this message]
2004-09-10 3:34 ` Joel n.solanki
2004-09-10 14:36 ` zytek
2004-09-11 3:52 ` Joel n.solanki
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=41408AE0.30608@pobox.com \
--to=andre.correa@pobox.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.