From: Mike Rapoport <rppt@linux.ibm.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM/BPF TOPIC] Page table manipulation primitives
Date: Thu, 6 Feb 2020 18:57:41 +0200 [thread overview]
Message-ID: <20200206165741.GC17499@linux.ibm.com> (raw)
While updating the architectures to properly use 5-level folded page tables
without <asm-generic/?level-fixup.h> and <asm-generic/pgtable-nop4d-hack.h>
I wondered if we can do better than explicitly name each and every level of
the page table, open-code traversal of all the layers numerous times and
have copied do_something_pXd_range().
Then I've come across Kirill's "Proof-of-concept: better(?) page-table
manipulation API" [1], but as far as I could see there was no progress
since then.
I'd like to resurrect the topic and try to see if we can come up with
actually better page table manipulation API.
[1] https://lore.kernel.org/lkml/20180424154355.mfjgkf47kdp2by4e@black.fi.intel.com/
--
Sincerely yours,
Mike.
next reply other threads:[~2020-02-06 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:57 Mike Rapoport [this message]
2020-02-06 17:34 ` Matthew Wilcox
2020-02-07 17:45 ` Kirill A. Shutemov
2020-02-07 19:40 ` Matthew Wilcox
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=20200206165741.GC17499@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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