Hello,
On Sun, Mar 14, 2021 at 01:58:33PM -0700, Shakeel Butt wrote:
> > If my understanding were correct, what Tejun suggested is to add a fast
> > read interface to rstat to be used in hot path. And its accuracy is
> > similar as that of traditional per-CPU counter. But if we can regularly
> >
On Thu, Mar 11, 2021 at 12:52 AM Huang, Ying wrote:
>
> Hi, Butt,
>
> Shakeel Butt writes:
>
> > On Wed, Mar 10, 2021 at 4:47 PM Huang, Ying wrote:
> >>
> >> From: Huang Ying
> >>
> >> In shrink_node(), to determine whether to enable cache trim mode, the
> >> LRU size is gotten via lruvec_page_
Hi, Butt,
Shakeel Butt writes:
> On Wed, Mar 10, 2021 at 4:47 PM Huang, Ying wrote:
>>
>> From: Huang Ying
>>
>> In shrink_node(), to determine whether to enable cache trim mode, the
>> LRU size is gotten via lruvec_page_state(). That gets the value from
>> a per-CPU counter (mem_cgroup_per_n
On Wed, Mar 10, 2021 at 4:47 PM Huang, Ying wrote:
>
> From: Huang Ying
>
> In shrink_node(), to determine whether to enable cache trim mode, the
> LRU size is gotten via lruvec_page_state(). That gets the value from
> a per-CPU counter (mem_cgroup_per_node->lruvec_stat[]). The error of
> the p
From: Huang Ying
In shrink_node(), to determine whether to enable cache trim mode, the
LRU size is gotten via lruvec_page_state(). That gets the value from
a per-CPU counter (mem_cgroup_per_node->lruvec_stat[]). The error of
the per-CPU counter from CPU local counting and the descendant memory
5 matches
Mail list logo