From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: kent.overstreet@linux.dev, corbet@lwn.net, arnd@arndb.de,
mcgrof@kernel.org, rppt@kernel.org, paulmck@kernel.org,
thuth@redhat.com, tglx@linutronix.de, bp@alien8.de,
xiongwei.song@windriver.com, ardb@kernel.org, david@redhat.com,
vbabka@suse.cz, mhocko@suse.com, hannes@cmpxchg.org,
roman.gushchin@linux.dev, dave@stgolabs.net, willy@infradead.org,
liam.howlett@oracle.com, pasha.tatashin@soleen.com,
souravpanda@google.com, keescook@chromium.org, dennis@kernel.org,
jhubbard@nvidia.com, urezki@gmail.com, hch@infradead.org,
petr.pavlu@suse.com, samitolvanen@google.com,
da.gomez@samsung.com, yuzhao@google.com, vvvvvv@google.com,
rostedt@goodmis.org, iamjoonsoo.kim@lge.com, rientjes@google.com,
minchan@google.com, kaleshsingh@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
maple-tree@lists.infradead.org, linux-modules@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v4 5/6] alloc_tag: introduce pgtag_ref_handle to abstract page tag references
Date: Wed, 23 Oct 2024 14:00:17 -0700 [thread overview]
Message-ID: <20241023140017.e165544bf20bcb0c79bfee57@linux-foundation.org> (raw)
In-Reply-To: <20241023170759.999909-6-surenb@google.com>
On Wed, 23 Oct 2024 10:07:58 -0700 Suren Baghdasaryan <surenb@google.com> wrote:
> To simplify later changes to page tag references, introduce new
> pgtag_ref_handle type. This allows easy replacement of page_ext
> as a storage of page allocation tags.
>
> ...
>
> static inline void pgalloc_tag_copy(struct folio *new, struct folio *old)
> {
> + union pgtag_ref_handle handle;
> + union codetag_ref ref;
> struct alloc_tag *tag;
> - union codetag_ref *ref;
>
> tag = pgalloc_tag_get(&old->page);
> if (!tag)
> return;
>
> - ref = get_page_tag_ref(&new->page);
> - if (!ref)
> + if (!get_page_tag_ref(&new->page, &ref, &handle))
> return;
>
> /* Clear the old ref to the original allocation tag. */
> clear_page_tag_ref(&old->page);
> /* Decrement the counters of the tag on get_new_folio. */
> - alloc_tag_sub(ref, folio_nr_pages(new));
> -
> - __alloc_tag_ref_set(ref, tag);
> -
> - put_page_tag_ref(ref);
> + alloc_tag_sub(&ref, folio_nr_pages(new));
mm-stable has folio_size(new) here, fixed up.
I think we aleady discussed this, but there's a crazy amount of
inlining here. pgalloc_tag_split() is huge, and has four callsites.
next prev parent reply other threads:[~2024-10-23 21:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:07 [PATCH v4 0/6] page allocation tag compression Suren Baghdasaryan
2024-10-23 17:07 ` [PATCH v4 1/6] maple_tree: add mas_for_each_rev() helper Suren Baghdasaryan
2024-10-23 17:24 ` Pasha Tatashin
2024-10-23 17:07 ` [PATCH v4 2/6] alloc_tag: introduce shutdown_mem_profiling helper function Suren Baghdasaryan
2024-10-23 17:26 ` Pasha Tatashin
2024-10-23 17:07 ` [PATCH v4 3/6] alloc_tag: load module tags into separate contiguous memory Suren Baghdasaryan
2024-10-23 18:05 ` Pasha Tatashin
2024-10-23 17:07 ` [PATCH v4 4/6] alloc_tag: populate memory for module tags as needed Suren Baghdasaryan
2024-10-23 18:28 ` Pasha Tatashin
2024-10-23 17:07 ` [PATCH v4 5/6] alloc_tag: introduce pgtag_ref_handle to abstract page tag references Suren Baghdasaryan
2024-10-23 17:35 ` Pasha Tatashin
2024-10-23 21:00 ` Andrew Morton [this message]
2024-10-23 21:09 ` Suren Baghdasaryan
2024-10-24 16:25 ` Suren Baghdasaryan
2024-10-23 17:07 ` [PATCH v4 6/6] alloc_tag: support for page allocation tag compression Suren Baghdasaryan
2024-10-23 18:29 ` Pasha Tatashin
2024-10-24 3:48 ` Suren Baghdasaryan
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=20241023140017.e165544bf20bcb0c79bfee57@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jhubbard@nvidia.com \
--cc=kaleshsingh@google.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=kernel-team@android.com \
--cc=liam.howlett@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=maple-tree@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=pasha.tatashin@soleen.com \
--cc=paulmck@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=vvvvvv@google.com \
--cc=willy@infradead.org \
--cc=xiongwei.song@windriver.com \
--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