From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org, devik@cdi.cz
Subject: Re: net-sched 01/05: add dynamically sized qdisc class hash helpers
Date: Thu, 03 Jul 2008 14:16:40 +0200 [thread overview]
Message-ID: <486CC328.5070107@trash.net> (raw)
In-Reply-To: <20080703121824.GA2559@ami.dom.local>
Jarek Poplawski wrote:
>> +static inline void *qdisc_class_find(struct Qdisc_class_hash *hash, u32 id)
>>
>
> Why not Qdisc_class_common *?
>
I originally didn't use container_of but simply required
Qdisc_class_common to be the first element of the
class struct, this is a remnant of that. I'll change it,
thanks.
>> +void qdisc_class_hash_grow(struct Qdisc *sch, struct Qdisc_class_hash *clhash)
>> +{
>> + struct Qdisc_class_common *cl;
>> + struct hlist_node *n, *next;
>> + struct hlist_head *nhash, *ohash;
>> + unsigned int nsize, nmask, osize;
>> + unsigned int i, h;
>> +
>> + /* Rehash when load factor exceeds 0.75 */
>> + if (clhash->hashelems * 4 <= clhash->hashsize * 3)
>>
>
> With current init hashsize == 4 this will trigger after adding: 4th,
> 7th, 13th,... class. Maybe we could start with something higher?
>
We could, but I don't think it makes any difference, for those
small numbers the rehashing is really cheap.
>> + return;
>> + nsize = clhash->hashsize * 2;
>> + nmask = nsize - 1;
>> + nhash = qdisc_class_hash_alloc(nsize);
>> + if (nhash == NULL)
>> + return;
>> +
>> + ohash = clhash->hash;
>> + osize = clhash->hashsize;
>> +
>> + sch_tree_lock(sch);
>> + for (i = 0; i < osize; i++) {
>> + hlist_for_each_entry_safe(cl, n, next, &ohash[i], hnode) {
>> + h = qdisc_class_hash(cl->classid, nmask);
>> + hlist_add_head(&cl->hnode, &nhash[h]);
>>
>
> With a large number of classes and changes this could probably give
> noticable delays, so maybe there would be reasonable to add a
> possibility of user defined, ungrowable hashsize as well?
I don't think its really going to be noticable (the numbers are not
*that* large), but I'll try to get some numbers.
next prev parent reply other threads:[~2008-07-03 12:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 14:34 [RFC]: net-sched 00/05: dynamically sized class hashes Patrick McHardy
2008-07-01 14:34 ` net-sched 01/05: add dynamically sized qdisc class hash helpers Patrick McHardy
2008-07-03 12:18 ` Jarek Poplawski
2008-07-03 12:16 ` Patrick McHardy [this message]
2008-07-01 14:34 ` net-sched 02/05: sch_hfsc: use dynamic " Patrick McHardy
2008-07-01 14:34 ` net-sched 03/05: sch_cbq: " Patrick McHardy
2008-07-01 14:34 ` net-sched 04/05: sch_htb: move hash and sibling list removal to htb_delete Patrick McHardy
2008-07-02 8:15 ` Jarek Poplawski
2008-07-02 10:11 ` Patrick McHardy
2008-07-02 12:16 ` Jarek Poplawski
2008-07-02 12:25 ` Patrick McHardy
2008-07-02 21:14 ` Jarek Poplawski
2008-07-03 11:53 ` Patrick McHardy
2008-07-01 14:34 ` net-sched 05/05: sch_htb: use dynamic class hash helpers Patrick McHardy
2008-07-02 21:31 ` Jarek Poplawski
2008-07-03 11:55 ` Patrick McHardy
2008-07-02 2:50 ` [RFC]: net-sched 00/05: dynamically sized class hashes David Miller
2008-07-02 6:54 ` Martin Devera
2008-07-02 10:13 ` Patrick McHardy
2008-07-02 14:21 ` Patrick McHardy
2008-07-02 14:27 ` Martin Devera
2008-07-02 14:30 ` Patrick McHardy
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=486CC328.5070107@trash.net \
--to=kaber@trash.net \
--cc=devik@cdi.cz \
--cc=jarkao2@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).