From: Suren Baghdasaryan <surenb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sfr@canb.auug.org.au, kent.overstreet@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] lib: do limited memory accounting for modules with ARCH_NEEDS_WEAK_PER_CPU
Date: Wed, 3 Apr 2024 15:31:16 -0700 [thread overview]
Message-ID: <CAJuCfpGMDz7jKCLTVFZZB+XVAb9jfK79C1kNa7-BsYGDT7hj3w@mail.gmail.com> (raw)
In-Reply-To: <20240403145719.547d1083fede2cb4ca2c41ef@linux-foundation.org>
On Wed, Apr 3, 2024 at 2:57 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 2 Apr 2024 11:09:33 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
>
> > ARCH_NEEDS_WEAK_PER_CPU does not allow percpu variable definitions inside
> > a function, therefore memory allocation profiling can't use it. This
> > definition is used only for modules, so we still can account core kernel
> > allocations and for modules we can do limited allocation accounting by
> > charging all of them to a single counter. This is not ideal but better
>
> I'll queue this as a to-be-squashed fix against "lib: add allocation
> tagging support for memory allocation profiling", OK?
Yes, that would be ideal. Thank you!
prev parent reply other threads:[~2024-04-03 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:09 [PATCH 1/1] fixup! fix missing vmalloc.h includes Suren Baghdasaryan
2024-04-02 18:09 ` [PATCH 1/1] lib: do limited memory accounting for modules with ARCH_NEEDS_WEAK_PER_CPU Suren Baghdasaryan
2024-04-03 21:57 ` Andrew Morton
2024-04-03 22:31 ` Suren Baghdasaryan [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=CAJuCfpGMDz7jKCLTVFZZB+XVAb9jfK79C1kNa7-BsYGDT7hj3w@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
/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