From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udevd: de-duplicate strings in rules
Date: Wed, 12 Nov 2008 16:50:51 +0000 [thread overview]
Message-ID: <491B096B.7060604@tuffmail.co.uk> (raw)
In-Reply-To: <4919E8FB.2050809@tuffmail.co.uk>
Kay Sievers wrote:
> On Tue, Nov 11, 2008 at 22:23, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>> On Tue, Nov 11, 2008 at 21:20, Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
>>
>>> On my Ubuntu installation this removes 15k of duplicate strings,
>>> using a temporary index of about 25k.
>>>
>> Great. That looks nice.
>>
>> Thats's the diff of the rule dump before and after the patch:
>> ...
>> -[] shrunk to 64896 bytes tokens (5408 * 12 bytes), 57298 bytes buffer
>> -[] dumping 5408 (64896 bytes) tokens, 5818 (57298 bytes) strings
>> +[] shrunk to 64896 bytes tokens (5408 * 12 bytes), 18204 bytes buffer
>> +[] used 40512 bytes of string index nodes (844 * 48 bytes)
>> +[] dumping 5408 (64896 bytes) tokens, 1369 (18204 bytes) strings
>>
>
> I split the nodes and the childs in two independent arrays, so we got
> rid of the limit of 10 childs per node. I've got ~200 fully uses slots
> with the huge rules set here. Unlimited childs in the index removes
> another 3 kB of duplicates, and the temporary index seems also a bit
> smaller:
> shrunk to 64896 bytes tokens (5408 * 12 bytes), 15324 bytes buffer
> used 29456 bytes for index (1076 * 16 bytes nodes, 1020 * 12 bytes
> child links)
>
> Would be great, if you can check if it still works for you as expected. :)
>
Did you have a particular reason to keep the trie_root array? Now
there's no fixed limit on children, you could just use trie[1] as the
root node. Remove the special case for depth = 0. And initialize it's
value and length to 0, then you can remove the special case for len = 0.
Alan
next prev parent reply other threads:[~2008-11-12 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:20 [PATCH] udevd: de-duplicate strings in rules Alan Jenkins
2008-11-11 21:23 ` Kay Sievers
2008-11-12 5:11 ` Kay Sievers
2008-11-12 16:50 ` Alan Jenkins [this message]
2008-11-12 18:00 ` Kay Sievers
2008-11-12 18:05 ` Alan Jenkins
2008-11-12 18:20 ` Kay Sievers
2008-11-12 20:48 ` Alan Jenkins
2008-11-12 21:37 ` Kay Sievers
2008-11-13 10:12 ` Alan Jenkins
2008-11-13 19:03 ` Kay Sievers
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=491B096B.7060604@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-hotplug@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).