From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] [PATCH 4/6] rculfhash: Change lazy shrink strategy
Date: Wed, 02 Nov 2011 16:18:08 +0800 [thread overview]
Message-ID: <4EB0FCC0.7040009@cn.fujitsu.com> (raw)
In-Reply-To: <20111101170854.GG18068@Krystal>
On 11/02/2011 01:08 AM, Mathieu Desnoyers wrote:
> * Lai Jiangshan (laijs at cn.fujitsu.com) wrote:
>> We can aggressively grow a ht,
>
> What allows us to state that agressive grow is OK ?
I mean, if compare to shrinking, growing can be agressive a little more,
we can to do grow even the launching thread get old information.
But if compare to growing, shrinking must be conservative a little more,
if the launching thread find other thread are trying to grow ht,
it means the launching thread got old information, it should
stop to shrink.
I think I should used "relativistic agressive".
Thanks,
Lai
>
>
> missing space above.
>
>> + if (s <= count)
>> + return;
>
> Keeping the behavior of size check (change to patch 2) will probably
> affect this.
Waiting for your new reply for the patch 2.
>
>> +
>> + size = s;
>> + }
>> + }
>> +
>> __cds_lfht_resize_lazy_launch(ht);
>> }
>> --
>> 1.7.4.4
>>
>
next prev parent reply other threads:[~2011-11-02 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1320051657.git.laijs@cn.fujitsu.com>
[not found] ` <e790679beb8d966aa5dfc8205aaf844aee1546de.1320051657.git.laijs@cn.fujitsu.com>
2011-11-01 16:49 ` [ltt-dev] [PATCH 1/6] rculfhash: Fix ht allocation bug Mathieu Desnoyers
[not found] ` <a7d9cb37f37875bec47413d43274037be105bcf6.1320051657.git.laijs@cn.fujitsu.com>
2011-11-01 17:04 ` [ltt-dev] [PATCH 6/6] rculfhash: add min_alloc_size test parameter Mathieu Desnoyers
[not found] ` <1e66797f29e51b31e9f3b56dad65ac03651df526.1320051657.git.laijs@cn.fujitsu.com>
2011-11-01 17:00 ` [ltt-dev] [PATCH 2/6] rculfhash: Fix ht lazy grow logic Mathieu Desnoyers
2011-11-02 1:42 ` Lai Jiangshan
2011-11-02 15:13 ` Mathieu Desnoyers
2011-11-02 15:15 ` Mathieu Desnoyers
[not found] ` <bbea95bb9f3203390b69539a5801e1aff0eba3bc.1320051657.git.laijs@cn.fujitsu.com>
2011-11-01 17:06 ` [ltt-dev] [PATCH 3/6] rculfhash: merge duplicated code of cds_lfht_resize_lazy_*() Mathieu Desnoyers
2011-11-02 15:17 ` Mathieu Desnoyers
[not found] ` <23191cb487d53146a79f0fae67cfaa6287d5ab1c.1320051657.git.laijs@cn.fujitsu.com>
2011-11-01 17:08 ` [ltt-dev] [PATCH 4/6] rculfhash: Change lazy shrink strategy Mathieu Desnoyers
2011-11-02 8:18 ` Lai Jiangshan [this message]
2011-11-02 15:27 ` Mathieu Desnoyers
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=4EB0FCC0.7040009@cn.fujitsu.com \
--to=laijs@cn.fujitsu.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