From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kees Cook" <keescook@chromium.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: alloc: add __GFP_HIGHMEM flag
Date: Tue, 9 Jul 2024 09:55:18 +0200 [thread overview]
Message-ID: <CANiq72kO2rpPBf0Gxfqmt7cUMMsrH9kx0==63rthwXQD3fgAqw@mail.gmail.com> (raw)
In-Reply-To: <20240607-highmem-v1-1-d18c5ca4072f@google.com>
On Fri, Jun 7, 2024 at 10:23 AM Alice Ryhl <aliceryhl@google.com> wrote:
>
> Make it possible to allocate memory that doesn't need to mapped into the
> kernel's address space. This flag is useful together with
> Page::alloc_page [1].
>
> Rust Binder needs this for the memory that holds incoming transactions
> for each process. Each process will have a few megabytes of memory
> allocated with this flag, which is mapped into the process using
> vm_insert_page. When the kernel copies data for an incoming transaction
> into a process's memory region, it will use kmap_local_page to
> temporarily map pages that are being modified. There is no need for them
> to take up address space in the kernel when the kernel is not writing an
> incoming transaction into the page.
>
> Link: https://lore.kernel.org/all/20240528-alice-mm-v7-4-78222c31b8f4@google.com/ [1]
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Applied to `rust-next`, thanks!
Cheers,
Miguel
prev parent reply other threads:[~2024-07-09 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 8:23 Alice Ryhl
2024-07-09 7:55 ` Miguel Ojeda [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='CANiq72kO2rpPBf0Gxfqmt7cUMMsrH9kx0==63rthwXQD3fgAqw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wedsonaf@gmail.com \
--cc=willy@infradead.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