All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Simon Lodal <simonl@parknet.dk>,
	netdev@vger.kernel.org, lartc@mailman.ds9a.nl
Subject: Re: [PATCH] HTB O(1) class lookup
Date: Thu, 01 Feb 2007 08:06:24 -0500	[thread overview]
Message-ID: <1170335184.3915.8.camel@localhost> (raw)
In-Reply-To: <45C183EF.2040701@trash.net>

On Thu, 2007-01-02 at 07:08 +0100, Patrick McHardy wrote:

> 
> I have a patch for HFSC which introduces dynamic resizing of the
> class hash. 

One thing that has bitten me recently was tests to try and see how far i
can go insert xfrm SAD/SPDs - the resizing of the hashes kept allocing
more and more space until i ran out of memory, then swap took over and
hell broke loose. It would be nice in your approach to keep a
configurable upper bound on how much mem a hash table can chew.

> I have planned to generalize it (similar to tcf_hashinfo)
> and convert HTB and CBQ as well, which as a nice side effect will
> allow to get rid of some duplicated code, like hash walking.
> 

You know what would be really nice is a generic piece of code that would
apply for all sorts of netcode that uses hashes (theres a huge amount of
such code) and then converting over slowly all users to it: All
attributes to such hashes are known, max-size, hash() etc. The
tcf_hashinfo is a good start template for such an effort.

cheers,
jamal


  parent reply	other threads:[~2007-02-01 13:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01  5:18 [LARTC] [PATCH] HTB O(1) class lookup Simon Lodal
2007-02-01  5:18 ` Simon Lodal
2007-02-01  6:08 ` [LARTC] " Patrick McHardy
2007-02-01  6:08   ` Patrick McHardy
2007-02-01  7:08   ` [LARTC] " Simon Lodal
2007-02-01  7:08     ` Simon Lodal
2007-02-01 11:30     ` Andi Kleen
2007-02-05 10:16       ` [LARTC] " Jarek Poplawski
2007-02-05 10:16         ` Jarek Poplawski
2007-02-05 11:24         ` Andi Kleen
2007-02-05 12:45           ` Ingo Oeser
2007-02-05 17:14         ` [LARTC] " Simon Lodal
2007-02-05 17:14           ` Simon Lodal
2007-02-06  8:08           ` [LARTC] " Jarek Poplawski
2007-02-06  8:08             ` Jarek Poplawski
2007-02-08  7:36           ` [LARTC] " Jarek Poplawski
2007-02-08  7:36             ` Jarek Poplawski
2007-02-05 18:21       ` [LARTC] " Simon Lodal
2007-02-05 18:21         ` Simon Lodal
2007-02-01 13:06   ` jamal [this message]
2007-02-01 22:44 ` [LARTC] " Konrad Cempura

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=1170335184.3915.8.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=lartc@mailman.ds9a.nl \
    --cc=netdev@vger.kernel.org \
    --cc=simonl@parknet.dk \
    /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.