linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeel.butt@linux.dev>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
	vbabka@suse.cz,  rostedt@goodmis.org, peterz@infradead.org,
	yuzhao@google.com, minchan@google.com,  souravpanda@google.com,
	pasha.tatashin@soleen.com, 00107082@163.com,
	 quic_zhenhuah@quicinc.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm: avoid extra mem_alloc_profiling_enabled() checks
Date: Mon, 3 Feb 2025 12:36:51 -0800	[thread overview]
Message-ID: <vn7bns35qfeibasfgpinsrot4tipupcg5cjawrhobb4g2ibwor@6moxbtmo5l7m> (raw)
In-Reply-To: <20250201231803.2661189-1-surenb@google.com>

On Sat, Feb 01, 2025 at 03:18:00PM -0800, Suren Baghdasaryan wrote:
> Refactor code to avoid extra mem_alloc_profiling_enabled() checks inside
> pgalloc_tag_get() function which is often called after that check was
> already done.
> 
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>

Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>


      parent reply	other threads:[~2025-02-03 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01 23:18 Suren Baghdasaryan
2025-02-01 23:18 ` [PATCH v2 2/3] alloc_tag: uninline code gated by mem_alloc_profiling_key in slab allocator Suren Baghdasaryan
2025-02-03  8:23   ` Vlastimil Babka
2025-02-04  0:32   ` Shakeel Butt
2025-02-01 23:18 ` [PATCH v2 3/3] alloc_tag: uninline code gated by mem_alloc_profiling_key in page allocator Suren Baghdasaryan
2025-02-04  0:46   ` Shakeel Butt
2025-02-04 18:14     ` Suren Baghdasaryan
2025-02-03 20:36 ` Shakeel Butt [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=vn7bns35qfeibasfgpinsrot4tipupcg5cjawrhobb4g2ibwor@6moxbtmo5l7m \
    --to=shakeel.butt@linux.dev \
    --cc=00107082@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@google.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=peterz@infradead.org \
    --cc=quic_zhenhuah@quicinc.com \
    --cc=rostedt@goodmis.org \
    --cc=souravpanda@google.com \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=yuzhao@google.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