From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Deming Wang <wangdeming@inspur.com>,
Ira Weiny <ira.weiny@intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Catalin Marinas <catalin.marinas@arm.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Peter Collingbourne <pcc@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2] Documentation/mm: Add information about kmap_local_folio()
Date: Sun, 2 Jul 2023 00:54:32 +0100 [thread overview]
Message-ID: <ZKC8uE9fE57PuL91@casper.infradead.org> (raw)
In-Reply-To: <68a9b3aa-d064-ed6a-2bcd-9423eb4f595c@infradead.org>
On Sat, Jul 01, 2023 at 08:21:20AM -0700, Randy Dunlap wrote:
> > -* kmap_local_page(). This function is used to require short term mappings.
> > - It can be invoked from any context (including interrupts) but the mappings
> > - can only be used in the context which acquired them.
> > -
> > - This function should always be used, whereas kmap_atomic() and kmap() have
> > +* kmap_local_page(), kmap_local_folio() - These functions are used to require
>
> acquire ?
"create" might be better?
> > + short term mappings. They can be invoked from any context (including
> > + interrupts) but the mappings can only be used in the context which acquired
> > + them. The only differences between them consist in the first taking a pointer
> > + to a struct page and the second taking a pointer to struct folio and the byte
> > + offset within the folio which identifies the page.
>
> --
> ~Randy
next prev parent reply other threads:[~2023-07-01 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 14:19 Fabio M. De Francesco
2023-07-01 15:21 ` Randy Dunlap
2023-07-01 23:54 ` Matthew Wilcox [this message]
2023-07-01 23:59 ` Randy Dunlap
2023-07-02 13:05 ` Fabio M. De Francesco
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=ZKC8uE9fE57PuL91@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=wangdeming@inspur.com \
--cc=will@kernel.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