From: Simon Horman <horms@kernel.org>
To: Abel Wu <wuyun.abel@bytedance.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shakeel Butt <shakeelb@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 2/3] sock: Doc behaviors for pressure heurisitics
Date: Mon, 23 Oct 2023 08:49:40 +0100 [thread overview]
Message-ID: <20231023074940.GU2100445@kernel.org> (raw)
In-Reply-To: <20231019120026.42215-2-wuyun.abel@bytedance.com>
On Thu, Oct 19, 2023 at 08:00:25PM +0800, Abel Wu wrote:
> There are now two accounting infrastructures for skmem, while the
> heuristics in __sk_mem_raise_allocated() were actually introduced
> before memcg was born.
>
> Add some comments to clarify whether they can be applied to both
> infrastructures or not.
>
> Suggested-by: Shakeel Butt <shakeelb@google.com>
> Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
> Acked-by: Shakeel Butt <shakeelb@google.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-10-23 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 12:00 [PATCH net v3 1/3] sock: Code cleanup on __sk_mem_raise_allocated() Abel Wu
2023-10-19 12:00 ` [PATCH net v3 2/3] sock: Doc behaviors for pressure heurisitics Abel Wu
2023-10-23 7:49 ` Simon Horman [this message]
2023-10-19 12:00 ` [PATCH net v3 3/3] sock: Ignore memcg pressure heuristics when raising allocated Abel Wu
2023-10-23 7:49 ` Simon Horman
2023-10-24 7:08 ` Paolo Abeni
2023-10-24 7:35 ` Shakeel Butt
2023-10-24 8:21 ` Abel Wu
2023-10-23 7:49 ` [PATCH net v3 1/3] sock: Code cleanup on __sk_mem_raise_allocated() Simon Horman
2023-10-24 8:50 ` patchwork-bot+netdevbpf
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=20231023074940.GU2100445@kernel.org \
--to=horms@kernel.org \
--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 \
--cc=shakeelb@google.com \
--cc=wuyun.abel@bytedance.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;
as well as URLs for NNTP newsgroup(s).