From: "T.J. Mercier" <tjmercier@google.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>,
cgroups@vger.kernel.org
Subject: Re: [PATCH 1/4] memcg: initiate deprecation of v1 tcp accounting
Date: Wed, 14 Aug 2024 13:59:15 -0700 [thread overview]
Message-ID: <CABdmKX07o8ywPNoTDL_tM6qn46TXeLbhHoQEtBpFBXJkWdAc7A@mail.gmail.com> (raw)
In-Reply-To: <20240814202825.2694077-2-shakeel.butt@linux.dev>
On Wed, Aug 14, 2024 at 1:28 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> Memcg v1 provides opt-in TCP memory accounting feature. However it is
> mostly unused due to its performance impact on the network traffic. In
> v2, the TCP memory is accounted in the regular memory usage and is
> transparent to the users but they can observe the TCP memory usage
> through memcg stats.
>
> Let's initiate the deprecation process of memcg v1's tcp accounting
> functionality and add warnings to gather if there are any users and if
> there are, collect how they are using it and plan to provide them better
> alternative in v2.
>
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
> ---
> Documentation/admin-guide/cgroup-v1/memory.rst | 8 ++++++++
> mm/memcontrol-v1.c | 3 +++
> 2 files changed, 11 insertions(+)
>
> diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
> index 9cde26d33843..fb6d3e2a6395 100644
> --- a/Documentation/admin-guide/cgroup-v1/memory.rst
> +++ b/Documentation/admin-guide/cgroup-v1/memory.rst
> @@ -105,10 +105,18 @@ Brief summary of control files.
> memory.kmem.max_usage_in_bytes show max kernel memory usage recorded
>
> memory.kmem.tcp.limit_in_bytes set/show hard limit for tcp buf memory
> + This knob is deprecated and shouldn't be
> + used.
> memory.kmem.tcp.usage_in_bytes show current tcp buf memory allocation
> + This knob is deprecated and shouldn't be
> + used.
> memory.kmem.tcp.failcnt show the number of tcp buf memory usage
> + This knob is deprecated and shouldn't be
> + used.
> hits limits
Looks like you split the description (that has weird grammar) here.
> memory.kmem.tcp.max_usage_in_bytes show max tcp buf memory usage recorded
> + This knob is deprecated and shouldn't be
> + used.
> ==================================== ==========================================
>
> 1. History
> diff --git a/mm/memcontrol-v1.c b/mm/memcontrol-v1.c
> index 9725c731fb21..b8e2ee454eaa 100644
> --- a/mm/memcontrol-v1.c
> +++ b/mm/memcontrol-v1.c
> @@ -2447,6 +2447,9 @@ static ssize_t mem_cgroup_write(struct kernfs_open_file *of,
> ret = 0;
> break;
> case _TCP:
> + pr_warn_once("kmem.tcp.limit_in_bytes is deprecated and will be removed. "
> + "Please report your usecase to linux-mm@kvack.org if you "
> + "depend on this functionality.\n");
> ret = memcg_update_tcp_max(memcg, nr_pages);
> break;
> }
> --
> 2.43.5
>
Otherwise LGTM
Reviewed-by: T.J. Mercier <tjmercier@google.com>
next prev parent reply other threads:[~2024-08-14 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 20:28 [PATCH 0/4] memcg: initiate deprecation of v1 features Shakeel Butt
2024-08-14 20:28 ` [PATCH 1/4] memcg: initiate deprecation of v1 tcp accounting Shakeel Butt
2024-08-14 20:59 ` T.J. Mercier [this message]
2024-08-14 21:42 ` Shakeel Butt
2024-08-14 20:28 ` [PATCH 2/4] memcg: initiate deprecation of v1 soft limit Shakeel Butt
2024-08-14 20:28 ` [PATCH 3/4] memcg: initiate deprecation of oom_control Shakeel Butt
2024-08-14 21:00 ` T.J. Mercier
2024-08-14 21:41 ` Shakeel Butt
2024-08-14 21:49 ` Shakeel Butt
2024-08-14 21:51 ` Andrew Morton
2024-08-14 20:28 ` [PATCH 4/4] memcg: initiate deprecation of pressure_level Shakeel Butt
2024-08-14 21:01 ` T.J. Mercier
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=CABdmKX07o8ywPNoTDL_tM6qn46TXeLbhHoQEtBpFBXJkWdAc7A@mail.gmail.com \
--to=tjmercier@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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