From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Removing VM_LOCKED from user memory
Date: Wed, 25 Apr 2007 14:29:17 +0200 [thread overview]
Message-ID: <200704251429.26014.eike-kernel@sf-tec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Hi,
I need some assistance handling a large memory segment of a user process.
The user calls the kernel with a address and a length of it's own memory. My
driver will lock this memory using get_user_pages(). This memory is used as
DMA buffer directly from or to user processes.
Everything works fine that far: allocating, DMA mapping, DMA transfers. But I
currently can't get rid of the buffer again. Which function would help me to
get all pages unlocked once the buffer isn't needed anymore?
Is it enough to simply call sys_munlock() from the release and cleanup
functions?
There are no plans to share these mappings between different processes.
Greetings,
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2007-04-25 12:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200704251429.26014.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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