[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ce8b6e4-5abb-3edb-8423-f6c222420a89@suse.cz>
Date: Mon, 1 Feb 2021 16:17:51 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Yang Shi <shy828301@...il.com>
Cc: Roman Gushchin <guro@...com>, Kirill Tkhai <ktkhai@...tuozzo.com>,
Shakeel Butt <shakeelb@...gle.com>,
Dave Chinner <david@...morbit.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux MM <linux-mm@...ck.org>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [v5 PATCH 07/11] mm: vmscan: add per memcg shrinker nr_deferred
On 1/29/21 7:04 PM, Yang Shi wrote:
>> > > @@ -209,9 +214,15 @@ static int expand_one_shrinker_info(struct mem_cgroup *memcg,
>> > > if (!new)
>> > > return -ENOMEM;
>> > >
>> > > - /* Set all old bits, clear all new bits */
>> > > - memset(new->map, (int)0xff, old_size);
>> > > - memset((void *)new->map + old_size, 0, size - old_size);
>> > > + new->map = (unsigned long *)(new + 1);
>> > > + new->nr_deferred = (void *)new->map + m_size;
>> >
>> > This better be aligned to sizeof(atomic_long_t). Can we be sure about that?
>>
>> Good point. No, if unsigned long is 32 bit on some 64 bit machines.
>
> I think we could just change map to "u64" and guarantee struct
> shrinker_info is aligned to 64 bit.
What about changing to order, nr_deferred before map? Then the atomics are at
the beginning of allocated area, thus aligned.
Powered by blists - more mailing lists