From: sunil bhargo <marx_bhargav@yahoo.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "mounesh.b@gmail.com" <mounesh.b@gmail.com>
Subject: Question regarding pinning of memory
Date: Tue, 7 May 2024 07:47:58 +0000 (UTC) [thread overview]
Message-ID: <1076302825.4233137.1715068078694@mail.yahoo.com> (raw)
In-Reply-To: 1076302825.4233137.1715068078694.ref@mail.yahoo.com
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hi, We have written an application that would open a device and then mmap it. In the kernel module the memory is allocated using vmalloc (don't require contiguous physical memory) and in mmap we are calling remap_pfn_range to map the memory to user space. The question is would this mechanism be enough that the memory would be pinned (neither swappable nor the page migration would happen) ?
Thanks,Sunil Bhargo
[-- Attachment #2: Type: text/html, Size: 1409 bytes --]
next parent reply other threads:[~2024-05-07 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1076302825.4233137.1715068078694.ref@mail.yahoo.com>
2024-05-07 7:47 ` sunil bhargo [this message]
2024-05-07 8:09 ` Question regarding pinning of memory David Hildenbrand
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=1076302825.4233137.1715068078694@mail.yahoo.com \
--to=marx_bhargav@yahoo.com \
--cc=linux-mm@kvack.org \
--cc=mounesh.b@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).