Re: [PATCH 00/40] Memory allocation profiling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Suren Baghdasaryan <surenb@xxxxxxxxxx>
Subject: Re: [PATCH 00/40] Memory allocation profiling
From: Johannes Weiner <hannes@xxxxxxxxxxx>
Date: Wed, 3 May 2023 16:11:50 -0400
Cc: Tejun Heo <tj@xxxxxxxxxx>, Kent Overstreet <kent.overstreet@xxxxxxxxx>, Michal Hocko <mhocko@xxxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, vbabka@xxxxxxx, roman.gushchin@xxxxxxxxx, mgorman@xxxxxxx, dave@xxxxxxxxxxxx, willy@xxxxxxxxxxxxx, liam.howlett@xxxxxxxxxx, corbet@xxxxxxx, void@xxxxxxxxxxxxx, peterz@xxxxxxxxxxxxx, juri.lelli@xxxxxxxxxx, ldufour@xxxxxxxxxxxxx, catalin.marinas@xxxxxxx, will@xxxxxxxxxx, arnd@xxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxxxxx, dave.hansen@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, peterx@xxxxxxxxxx, david@xxxxxxxxxx, axboe@xxxxxxxxx, mcgrof@xxxxxxxxxx, masahiroy@xxxxxxxxxx, nathan@xxxxxxxxxx, dennis@xxxxxxxxxx, muchun.song@xxxxxxxxx, rppt@xxxxxxxxxx, paulmck@xxxxxxxxxx, pasha.tatashin@xxxxxxxxxx, yosryahmed@xxxxxxxxxx, yuzhao@xxxxxxxxxx, dhowells@xxxxxxxxxx, hughd@xxxxxxxxxx, andreyknvl@xxxxxxxxx, keescook@xxxxxxxxxxxx, ndesaulniers@xxxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, ebiggers@xxxxxxxxxx, ytcoode@xxxxxxxxx, vincent.guittot@xxxxxxxxxx, dietmar.eggemann@xxxxxxx, rostedt@xxxxxxxxxxx, bsegall@xxxxxxxxxx, bristot@xxxxxxxxxx, vschneid@xxxxxxxxxx, cl@xxxxxxxxx, penberg@xxxxxxxxxx, iamjoonsoo.kim@xxxxxxx, 42.hyeyoo@xxxxxxxxx, glider@xxxxxxxxxx, elver@xxxxxxxxxx, dvyukov@xxxxxxxxxx, shakeelb@xxxxxxxxxx, songmuchun@xxxxxxxxxxxxx, jbaron@xxxxxxxxxx, rientjes@xxxxxxxxxx, minchan@xxxxxxxxxx, kaleshsingh@xxxxxxxxxx, kernel-team@xxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, iommu@xxxxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-modules@xxxxxxxxxxxxxxx, kasan-dev@xxxxxxxxxxxxxxxx, cgroups@xxxxxxxxxxxxxxx, Alexei Starovoitov <ast@xxxxxxxxxx>, Andrii Nakryiko <andrii@xxxxxxxxxx>
In-reply-to: <CAJuCfpG4TmRpT5iU7bJmKcjW2Tghstdo1b=qEG=tDsmtJQYuWA@mail.gmail.com>
References: <ZFKNZZwC8EUbOLMv@slm.duckdns.org> <20230503180726.GA196054@cmpxchg.org> <ZFKlrP7nLn93iIRf@slm.duckdns.org> <ZFKqh5Dh93UULdse@slm.duckdns.org> <ZFKubD/lq7oB4svV@moria.home.lan> <ZFKu6zWA00AzArMF@slm.duckdns.org> <ZFKxcfqkUQ60zBB_@slm.duckdns.org> <CAJuCfpEPkCJZO2svT-GfmpJ+V-jSLyFDKM_atnqPVRBKtzgtnQ@mail.gmail.com> <ZFK6pwOelIlhV8Bm@slm.duckdns.org> <CAJuCfpG4TmRpT5iU7bJmKcjW2Tghstdo1b=qEG=tDsmtJQYuWA@mail.gmail.com>

On Wed, May 03, 2023 at 01:08:40PM -0700, Suren Baghdasaryan wrote:
> On Wed, May 3, 2023 at 12:49 PM Tejun Heo <tj@xxxxxxxxxx> wrote:
> > * Improving memory allocation visibility makes sense to me. To me, a more
> >   natural place for that feels like /proc/allocations next to other memory
> >   info files rather than under debugfs.
> 
> TBH I would love that if this approach is acceptable.

Ack

References:
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Johannes Weiner
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Kent Overstreet
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Suren Baghdasaryan
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Tejun Heo
- Re: [PATCH 00/40] Memory allocation profiling
  - From: Suren Baghdasaryan

Prev by Date: Re: [PATCH 00/40] Memory allocation profiling
Next by Date: Re: [PATCH 00/40] Memory allocation profiling
Previous by thread: Re: [PATCH 00/40] Memory allocation profiling
Next by thread: Re: [PATCH 00/40] Memory allocation profiling
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [Monitors]