From: Abel Wu <wuyun.abel@bytedance.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] sock: Fix misuse of sk_under_memory_pressure()
Date: Wed, 10 May 2023 22:40:31 +0800 [thread overview]
Message-ID: <c4453efb-34a7-7a09-b179-e3e17b8074cc@bytedance.com> (raw)
In-Reply-To: <CANn89iK154B-NzRFymx_ggO9ZuVW-0YyHEKi6C46zjHpdRfokQ@mail.gmail.com>
Hi Eric, thanks very much for comments!
On 5/9/23 4:55 PM, Eric Dumazet wrote:
> On Sat, May 6, 2023 at 10:59 AM Abel Wu <wuyun.abel@bytedance.com> wrote:
>>
>> The commit 180d8cd942ce ("foundations of per-cgroup memory pressure
>> controlling") wrapped proto::memory_pressure status into an accessor
>> named sk_under_memory_pressure(), and in the next commit e1aab161e013
>> ("socket: initial cgroup code") added the consideration of net-memcg
>> pressure into this accessor.
>>
>> But with the former patch applied, not all of the call sites of
>> sk_under_memory_pressure() are interested in net-memcg's pressure.
>> The __sk_mem_{raise,reduce}_allocated() only focus on proto/netns
>> pressure rather than net-memcg's. IOW this accessor are generally
>> used for deciding whether should reclaim or not.
>>
>> Fixes: e1aab161e013 ("socket: initial cgroup code")
>> Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
>> ---
>> include/net/sock.h | 5 -----
>> net/core/sock.c | 17 +++++++++--------
>> 2 files changed, 9 insertions(+), 13 deletions(-)
>>
>> diff --git a/include/net/sock.h b/include/net/sock.h
>> index 8b7ed7167243..752d51030c5a 100644
>> --- a/include/net/sock.h
>> +++ b/include/net/sock.h
>> @@ -1404,11 +1404,6 @@ static inline int sk_under_cgroup_hierarchy(struct sock *sk,
>> #endif
>> }
>>
>> -static inline bool sk_has_memory_pressure(const struct sock *sk)
>> -{
>> - return sk->sk_prot->memory_pressure != NULL;
>> -}
>> -
>> static inline bool sk_under_memory_pressure(const struct sock *sk)
>> {
>> if (!sk->sk_prot->memory_pressure)
>> diff --git a/net/core/sock.c b/net/core/sock.c
>> index 5440e67bcfe3..8d215f821ea6 100644
>> --- a/net/core/sock.c
>> +++ b/net/core/sock.c
>> @@ -3017,13 +3017,14 @@ int __sk_mem_raise_allocated(struct sock *sk, int size, int amt, int kind)
>> }
>> }
>>
>> - if (sk_has_memory_pressure(sk)) {
>> - u64 alloc;
>> -
>> - if (!sk_under_memory_pressure(sk))
>> - return 1;
>> - alloc = sk_sockets_allocated_read_positive(sk);
>> - if (sk_prot_mem_limits(sk, 2) > alloc *
>> + if (prot->memory_pressure) {
>
> I do not understand this patch.
>
> Changelog is evasive, I do not see what practical problem you want to solve.
>
> sk_has_memory_pressure() is not about memcg, simply the fact that a
> proto has a non NULL memory_pressure pointer.
Sorry for failed to provide a reasonable explanation... Would you please
check my reply to Paolo?
Thanks,
Abel
prev parent reply other threads:[~2023-05-10 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 8:59 Abel Wu
2023-05-09 7:52 ` Paolo Abeni
2023-05-10 14:35 ` Abel Wu
2023-05-15 7:04 ` Abel Wu
2023-05-15 7:21 ` Eric Dumazet
2023-05-15 10:20 ` Abel Wu
2023-05-09 8:55 ` Eric Dumazet
2023-05-10 14:40 ` Abel Wu [this message]
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=c4453efb-34a7-7a09-b179-e3e17b8074cc@bytedance.com \
--to=wuyun.abel@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®