linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Sedlak <daniel.sedlak@cdn77.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Neal Cardwell <ncardwell@google.com>,
	David Ahern <dsahern@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	Matyas Hurtik <matyas.hurtik@cdn77.com>,
	Daniel Sedlak <danie.sedlak@cdn77.com>
Subject: Re: [PATCH v2 net-next 2/2] mm/vmpressure: add tracepoint for socket pressure detection
Date: Wed, 16 Jul 2025 10:47:42 +0200	[thread overview]
Message-ID: <ad52a9ca-bbbb-469f-8b8d-6a0f24ac3175@cdn77.com> (raw)
In-Reply-To: <CAAVpQUD=diV7aWqJqyQjL7MOZuC5xQ0AwJssPJ6vu4nYZPer+g@mail.gmail.com>

Hi Kuniyuki,

On 7/15/25 7:46 PM, Kuniyuki Iwashima wrote:
>>>> Maybe a noob question: How can we translate the memcg ID
>>>> to the /sys/fs/cgroup/... path ?
>>>
>>> IMO this should be really named `cgroup_id` instead of `memcg_id`, but
>>> we kept the latter to keep consistency with the rest of the file.
>>>
>>> To find cgroup path you can use:
>>> - find /sys/fs/cgroup/ -inum `memcg_id`, and it will print "path" to the
>>> affected cgroup.
>>> - or you can use bpftrace tracepoint hooks and there is a helper
>>> function [1].
>>
>> Thanks, this is good to know and worth in the commit message.

Sure, I will add it to the v3.

>>>> It would be nice to place this patch first and the description of
>>>> patch 2 has how to use the new stat with this tracepoint.
>>>
>>> Sure, can do that. However, I am unsure how a good idea is to
>>> cross-reference commits, since each may go through a different tree
>>> because each commit is for a different subsystem. They would have to go
>>> through one tree, right?
>>
>> Right.
> 
> Sorry, I meant to say the two patches don't need to go along to a
> single tree and you can post them separately as each change is
> independent.

Just to make sure we are on the same page. Are you suggesting first 
posting this second patch to mm, and once (if) it gets merged, reference 
it from the first patch and send the first patch to netdev?

Thanks!
Daniel


      reply	other threads:[~2025-07-16  8:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 14:36 [PATCH v2 net-next 0/2] account for TCP memory pressure signaled by cgroup Daniel Sedlak
2025-07-14 14:36 ` [PATCH v2 net-next 1/2] tcp: account for " Daniel Sedlak
2025-07-16 16:49   ` Shakeel Butt
2025-07-16 18:07     ` Kuniyuki Iwashima
2025-07-16 18:37       ` Shakeel Butt
2025-07-17 15:31       ` Daniel Sedlak
2025-07-17 17:26         ` Kuniyuki Iwashima
2025-07-14 14:36 ` [PATCH v2 net-next 2/2] mm/vmpressure: add tracepoint for socket pressure detection Daniel Sedlak
2025-07-14 18:02   ` Kuniyuki Iwashima
2025-07-15  7:01     ` Daniel Sedlak
2025-07-15 17:17       ` Kuniyuki Iwashima
2025-07-15 17:46         ` Kuniyuki Iwashima
2025-07-16  8:47           ` Daniel Sedlak [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=ad52a9ca-bbbb-469f-8b8d-6a0f24ac3175@cdn77.com \
    --to=daniel.sedlak@cdn77.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=danie.sedlak@cdn77.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-mm@kvack.org \
    --cc=matyas.hurtik@cdn77.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shakeel.butt@linux.dev \
    --cc=yosry.ahmed@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