All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ and all other qdiscs now REALLY completely documented (almost!)
Date: Mon, 03 Dec 2001 02:53:02 +0000	[thread overview]
Message-ID: <marc-lartc-100734788910984@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100734471005654@msgid-missing>

On Sun, Dec 02, 2001 at 11:45:57PM -0300, Alberto Bertogli wrote:

> > SFQ doesn't shape, so it's a whole different ballgame. 
> 
> Yeah, I shape with CBQ anyway.. what reminds me to my next question: is
> HTB going to be merged in 2.4? is it ready for production use?

I think HTB is ready. Martin is on top of things and is rapidly cleaning up
remaining issues. He is now asking the networking maintainers of Linux for
advice on what needs to be done.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

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

  parent reply	other threads:[~2001-12-03  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  1:58 [LARTC] CBQ and all other qdiscs now REALLY completely documented (almost!) bert hubert
2001-12-03  2:26 ` Jim Fleming
2001-12-03  2:45 ` Alberto Bertogli
2001-12-03  2:53 ` bert hubert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-01  0:33 Finally, CBQ nearly completely documented bert hubert
2001-12-03  2:00 ` CBQ and all other qdiscs now REALLY completely documented (almost!) bert hubert
2001-12-03  2:26   ` [LARTC] " Jim Fleming

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-100734788910984@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.