linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas@tungstengraphics.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org
Subject: Re: Driver-driven paging?
Date: Mon, 09 Oct 2006 19:45:42 +0200	[thread overview]
Message-ID: <452A8AC6.2080203@tungstengraphics.com> (raw)
In-Reply-To: <452A7AD3.5050006@yahoo.com.au>

Nick Piggin wrote:

> Thomas Hellstrom wrote:
>
>> Hi!
>>
>> While trying to put together an improved graphics memory manager in 
>> the DRM kernel module, I've identified a need to swap out backing 
>> store pages which haven't been in use for a while, and I was 
>> wondering if there is a kernel mm API to do that?
>>
>> Basically when a graphics object is created, space is allocated 
>> either in on-card video RAM or in a backup object in system RAM. That 
>> backup object can optionally be flipped into the AGP aperture for 
>> fast and linear graphics card access.
>>
>> What I want to do is to be able to release backup object pages while 
>> maintaining the contents. Basically hand them over to the swapping 
>> system and get a handle back that can be used for later retrieval. 
>> The driver will unmap all mappings referencing the page before 
>> handing it over to the swapping system.
>>
>> Is there an API for this and is there any chance of getting it exported?
>
>
> I suspect you will run into a few troubles trying to do it all in kernel.
> It might be possible, but probably not with the current code, and it
> isn't clear we'd want to make the required changes to support such a
> thing.
>
> 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.
>
Hi!

I was actually thinking of something similar, but I thought it would be 
cleaner to do it in the kernel, if the API were there. But currently the 
DRM needs a "master" user-space process anyway so it's a feasible way to go.

> If you need for the driver to *then* export these pages out to be mapped
> by other processes in userspace, I think you run into problems if trying
> to use nopage. You'll need to go the nopfn route (and thus your mappings
> must disallow PROT_WRITE && MAP_PRIVATE).
>
> But I think that might just work?
>
Yes, possibly. What kind of problems would I expect if using nopage? Is 
it, in particular, legal for a process to call get_user_pages() with the 
tsk and mm arguments of another process?

Thanks,

Thomas



--
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>

  reply	other threads:[~2006-10-09 17:45 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 [this message]
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

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=452A8AC6.2080203@tungstengraphics.com \
    --to=thomas@tungstengraphics.com \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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