From: Andrew Morton <akpm@linux-foundation.org>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
"David S. Miller" <davem@davemloft.net>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>,
linux-mm@kvack.org, Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH] memcg: Keep socket_pressure fresh on 32-bit kernel.
Date: Wed, 16 Jul 2025 15:43:15 -0700 [thread overview]
Message-ID: <20250716154315.b49d3af2cd9294faea24d6c2@linux-foundation.org> (raw)
In-Reply-To: <20250716042925.106239-1-kuniyu@google.com>
On Wed, 16 Jul 2025 04:29:12 +0000 Kuniyuki Iwashima <kuniyu@google.com> wrote:
> memcg->socket_pressure is initialised with jiffies when the memcg
> is created.
>
> Once vmpressure detects that the cgroup is under memory pressure,
> the field is updated with jiffies + HZ to signal the fact to the
> socket layer and suppress memory allocation for one second.
>
> Otherwise, the field is not updated.
>
> mem_cgroup_under_socket_pressure() uses time_before() to check if
> jiffies is less than memcg->socket_pressure, and this has a bug on
> 32-bit kernel.
>
> if (time_before(jiffies, memcg->socket_pressure))
> return true;
>
> As time_before() casts the final result to long, the acceptable delta
> between two timestamps is 2 ^ (BITS_PER_LONG - 1).
>
> On 32-bit kernel with CONFIG_HZ=1000, this is about 24 days.
>
> >>> (2 ** 31) / 1000 / 60 / 60 / 24
> 24.855134814814818
>
> Once 24 days have passed since the last update of socket_pressure,
> mem_cgroup_under_socket_pressure() starts to lie until the next
> 24 days pass.
>
> Thus, we need to update socket_pressure to a recent timestamp
> periodically on 32-bit kernel.
>
> Let's do that every 24 hours, with a variation of about 0 to 4 hours.
Can't we simply convert ->socket_preesure to a 64-bit type?
timespec64/time64_t/etc?
next prev parent reply other threads:[~2025-07-16 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 4:29 Kuniyuki Iwashima
2025-07-16 19:59 ` Shakeel Butt
2025-07-16 21:16 ` Kuniyuki Iwashima
2025-07-16 22:43 ` Andrew Morton [this message]
2025-07-16 23:13 ` Kuniyuki Iwashima
2025-07-16 23:52 ` Andrew Morton
2025-07-16 23:58 ` Kuniyuki Iwashima
2025-07-17 1:02 ` Andrew Morton
2025-07-17 19:37 ` Kuniyuki Iwashima
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=20250716154315.b49d3af2cd9294faea24d6c2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hannes@cmpxchg.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=linux-mm@kvack.org \
--cc=ncardwell@google.com \
--cc=vdavydov.dev@gmail.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