From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: linux-mm@kvack.org
Subject: Kernel tempory memory alloc
Date: Sat, 19 Nov 2005 12:45:51 +0000 [thread overview]
Message-ID: <437F1E7F.40504@superbug.demon.co.uk> (raw)
Hi,
I am going to implement an IOCTL for a particular driver.
Previously I might have used the stack to store the request/response in
while using copy_to/from_user, but with the 4K stack limit, I must
consider other alternatives.
The IOCTL will be a simple request/response type, so the memory
allocation will be for a very short time. Which is the correct memory
api to use when allocating short term temporary memory in the kernel.
Alternatively, is there a way to handle this by simply moving a page
from user space to kernel space and then back to user space again?
Thus reducing the amount of memcpy.
James
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2005-11-19 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 12:45 James Courtier-Dutton [this message]
2005-11-19 18:57 ` Fawad Lateef
2005-11-19 23:54 ` Andi Kleen
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=437F1E7F.40504@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--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