Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IMQ Install Without Recompiling Kernel?
Date: Thu, 25 Sep 2003 20:14:02 +0000	[thread overview]
Message-ID: <marc-lartc-106452095601256@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106425949122992@msgid-missing>

On Thursday 25 September 2003 21:51, Walter D. Wyndroski wrote:
> 1) Why is RH a bad choice?
I think RH changes too much.  If you you have a RH apache server and you want 
support from the apache community, you are out of luck.  The RH apache server 
is so much patched that can't help you.  And apt-get rocks :)

> 2) Why the sarcasm about not wanting to recompile the kernel? I love using
> Linux, and I have recompiled kernels before. However, in this application
> it may not be my best choice. You do not know my situation. I tried
> recompiling the kernel on this machine and had much trouble with the
> particular SCSI card in that machine. However, I felt this list was limited
> to routing issues and NOT kernel recompilation issues with a SCSI card.
If this is a closed binary, you still can recomile the kernel with the RH 
kernel sources.  I did this before.  I wanted to use a closed source binary 
to access tape drives on my debian server.  I used the RH kernel sources and 
the module loaded without any problem.

> 3) My boss prefers that we stay with the stock RH kernel. If that is not
> possible then I will recompile, but only if absolutely necessary.
I'm afraid a recompile is needed.

> 4) I'm not the qdisc or routing master, but from my reading I understand
> the following:
>         -An egress qdisc applied to eth0 ONLY shapes traffic leaving eth0,
> NOT eth1, eth2, etc.
Indeed.

>         -I don't want to write an egress qdisc for each of my 9 interfaces,
> plus I also want ingress control.
>         -With that said, I want a subnet to be limited to speed X megabits
> no matter if traffic is leaving or entering eth0, eth1, or any other
> interface.
If it's only rate limiting, you can try filter + policers.

> 5) I have different types of customers on each interface, hence different
> traffic flows and speeds.
If you only need to limit speed and don't care about how bandwidth is divided, 
the ingress qdisc + filters + policers can help you.

> 6) I have read this mailing list for well over a year now and enjoyed it
> quite a bit. I really appreciate all the members who help and give really
> good pointers.
Thx:)

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

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

  parent reply	other threads:[~2003-09-25 20:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 19:35 [LARTC] IMQ Install Without Recompiling Kernel? Walter D. Wyndroski
2003-09-23 19:29 ` Stef Coene
2003-09-23 19:36 ` David Boreham
2003-09-23 19:47 ` Stef Coene
2003-09-23 20:08 ` David Boreham
2003-09-23 23:35 ` Walter D. Wyndroski
2003-09-24 16:29 ` Stef Coene
2003-09-24 16:40 ` David Boreham
2003-09-24 23:30 ` Damjan
2003-09-25 19:39 ` Walter D. Wyndroski
2003-09-25 19:51 ` Walter D. Wyndroski
2003-09-25 20:14 ` Stef Coene [this message]
2003-09-25 20:26 ` David Boreham
2003-09-25 20:42 ` Daniel Chemko
2003-09-28 22:51 ` Walter D. Wyndroski

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=marc-lartc-106452095601256@msgid-missing \
    --to=stef.coene@docum.org \
    --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