From: Ingo Oeser <netdev@axxeo.de>
To: Andi Kleen <ak@suse.de>
Cc: Jarek Poplawski <jarkao2@o2.pl>, Simon Lodal <simonl@parknet.dk>,
Patrick McHardy <kaber@trash.net>,
netdev@vger.kernel.org, lartc@mailman.ds9a.nl
Subject: Re: [PATCH] HTB O(1) class lookup
Date: Mon, 5 Feb 2007 13:45:27 +0100 [thread overview]
Message-ID: <200702051345.27827.netdev@axxeo.de> (raw)
In-Reply-To: <200702051224.53777.ak@suse.de>
Andi Kleen schrieb:
> On Monday 05 February 2007 11:16, Jarek Poplawski wrote:
> > I wonder, why not try, at least for a while, to do this
> > a compile (menuconfig) option with a comment:
> > recommended for a large number of classes. After hash
> > optimization and some testing, final decisions could be
> > made.
>
> There are already far too many obscure CONFIGs. Don't add more.
And for people concerned about memory usage: There is always CONFIG_SMALL
for such decisions. Maybe one can limit worst case and average memory usage
based on this config. The algorithm should stay the same.
Regards
Ingo Oeser
next prev parent reply other threads:[~2007-02-05 12:45 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 [this message]
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
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=200702051345.27827.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=ak@suse.de \
--cc=jarkao2@o2.pl \
--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.