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] 3c905 or intel with 82550 chip?  for htb + bridge + (u32 & fw filters)
Date: Thu, 02 Jan 2003 21:58:52 +0000	[thread overview]
Message-ID: <marc-lartc-104154487302263@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104152880716719@msgid-missing>

On Thursday 02 January 2003 18:32, Victor Cassar wrote:
> Hi:
>
> finally i´m working with htb + bridge on 2.4.20 to
> shape ip traffic, and i want to build a system but i´m
> not up2date with these specific driver issues
>
> mi primary need is to shape small bandwidths 128 or
> 256
>
> are there any diferences between these 2 options?
> Since i need more granularity in the queuing
> behavior..i dont know how relevant this decision can
> be..
The chip doesn't mather.  All shaping is done in the kernel so in software.

Stef

-- 

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

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

  reply	other threads:[~2003-01-02 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 17:32 [LARTC] 3c905 or intel with 82550 chip? for htb + bridge + (u32 & fw filters) Victor Cassar
2003-01-02 21:58 ` Stef Coene [this message]
2003-01-02 22:30 ` [LARTC] 3c905 or intel with 82550 chip? for htb + bridge + William L. Thomson Jr.
2003-01-02 23:13 ` [LARTC] 3c905 or intel with 82550 chip? for htb + bridge + (u32 & fw filters) Victor Cassar
2003-01-03 17:17 ` Victor Cassar
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03  2:07 John Bäckstrand

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-104154487302263@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