From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rik van Riel <riel@surriel.com>
Cc: Thomas Hellstrom <thomas@tungstengraphics.com>, linux-mm@kvack.org
Subject: Re: Driver-driven paging?
Date: Fri, 13 Oct 2006 16:29:17 +1000 [thread overview]
Message-ID: <452F323D.2040600@yahoo.com.au> (raw)
In-Reply-To: <452E8849.8050201@surriel.com>
Rik van Riel wrote:
> Nick Piggin wrote:
>
>> Your best bet might be to have a userspace "memory manager" process,
>> which
>> allocates pages (anonymous or file backed), and has your device driver
>> access them with get_user_pages. The get_user_pages takes care of
>> faulting
>> the pages back in, and when they are released, the memory manager will
>> swap them out on demand.
>
>
> Wouldn't tmpfs be simpler ?
It could be... actually having the pages inserted into a tmpfs filesystem
by the kernel does sound better than having it try to use the swap code
directly. I still don't know that tmpfs could quite handle that yet, but it
does sound like an interesting avenue (or maybe making your own filesystem
using some tmpfs interfaces). Good idea.
For an initial cut, I think having a memory manager process will work today,
and should do everything needed. So it might be a good way to quickly
evaluate the functionality.
--
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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>
prev parent reply other threads:[~2006-10-13 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 15:21 Thomas Hellstrom
2006-10-09 16:37 ` Nick Piggin
2006-10-09 17:45 ` Thomas Hellström
2006-10-10 0:47 ` Nick Piggin
2006-10-10 6:04 ` Thomas Hellström
2006-10-12 18:24 ` Rik van Riel
2006-10-13 6:29 ` Nick Piggin [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=452F323D.2040600@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=thomas@tungstengraphics.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