netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com, devik@cdi.cz, hadi@cyberus.ca
Subject: Re: [PATCH 0/4]: Scalable HFSC
Date: Sun, 15 Aug 2004 19:42:23 -0700	[thread overview]
Message-ID: <20040815194223.18896b40.davem@redhat.com> (raw)
In-Reply-To: <411E6F49.9030303@trash.net>

On Sat, 14 Aug 2004 22:00:09 +0200
Patrick McHardy <kaber@trash.net> wrote:

> These 4 patches for 2.4/2.6 make HFSC more scalable by using rbtree's
> instead of sorted lists and an O(1) algorithm for adjusting childrens
> vt-offset. With these patches HFSC with 1024 active sibling classes
> performs only slightly worse (CPU-wise) than HTB. Each change has been
> well tested in tcsim, so I think nothing should break.

All applied, thanks Patrick.

      reply	other threads:[~2004-08-16  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 20:00 [PATCH 0/4]: Scalable HFSC Patrick McHardy
2004-08-16  2:42 ` David S. Miller [this message]

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=20040815194223.18896b40.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=devik@cdi.cz \
    --cc=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).