Hi Mike---
>>Hi Tang Junhui---
>>
>>I'm not really sure about this one. It changes the semantics of the
>>amount of work done-- nr_to_scan now means number of things to free
>>instead of the number to check.
>>
>The code seems to be designed as that, sc->nr_to_scan marks how much btree
>nodes to
Hi Mike---
>Hi Tang Junhui---
>
>I'm not really sure about this one. It changes the semantics of the
>amount of work done-- nr_to_scan now means number of things to free
>instead of the number to check.
>
The code seems to be designed as that, sc->nr_to_scan marks how much btree
nodes to scan in
Hi Tang Junhui---
I'm not really sure about this one. It changes the semantics of the
amount of work done-- nr_to_scan now means number of things to free
instead of the number to check.
If the system is under severe memory pressure, and most of the cache is
essential/actively used, this could gr
From: Tang Junhui
In bch_mca_scan(), nr btree nodes are expected to shrink, so the for(;;)
loop need to satisfy the condition freed < nr.
And since c->btree_cache_used always decrease after mca_data_free() calling
in for(;;) loop, so we need a auto variable to record c->btree_cache_used
before t