linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
	david@redhat.com,  vbabka@suse.cz, souravpanda@google.com,
	keescook@chromium.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] alloc_tag: introduce clear_page_tag_ref() helper function
Date: Wed, 14 Aug 2024 18:42:20 +0000	[thread overview]
Message-ID: <CA+CK2bBzRv70ECqkQOtvpPBuxKo=iAePgO5+UGuA7c9TwEfPqw@mail.gmail.com> (raw)
In-Reply-To: <20240813150758.855881-1-surenb@google.com>

On Tue, Aug 13, 2024 at 3:08 PM Suren Baghdasaryan <surenb@google.com> wrote:
>
> In several cases we are freeing pages which were not allocated using
> common page allocators. For such cases, in order to keep allocation
> accounting correct, we should clear the page tag to indicate that the
> page being freed is expected to not have a valid allocation tag.
> Introduce clear_page_tag_ref() helper function to be used for this.


Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>


      parent reply	other threads:[~2024-08-14 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 15:07 Suren Baghdasaryan
2024-08-13 15:07 ` [PATCH v3 2/2] alloc_tag: mark pages reserved during CMA activation as not tagged Suren Baghdasaryan
2024-08-13 15:09   ` David Hildenbrand
2024-08-13 16:06     ` Suren Baghdasaryan
2024-08-13 18:40   ` Andrew Morton
2024-08-13 19:37     ` Suren Baghdasaryan
2024-08-13 15:08 ` [PATCH v3 1/2] alloc_tag: introduce clear_page_tag_ref() helper function David Hildenbrand
2024-08-14 18:42 ` Pasha Tatashin [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='CA+CK2bBzRv70ECqkQOtvpPBuxKo=iAePgO5+UGuA7c9TwEfPqw@mail.gmail.com' \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=souravpanda@google.com \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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