From: Huang Shijie <shijie8@gmail.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: Does get_user_pages_fast lock the user pages in memory in my case?
Date: Mon, 20 Apr 2009 13:42:02 +0800 [thread overview]
Message-ID: <49EC0B2A.5080600@gmail.com> (raw)
In-Reply-To: <20090420142422.ff1a2a66.minchan.kim@barrios-desktop>
Minchan Kim a??e??:
> On Mon, 20 Apr 2009 13:05:33 +0800
> Huang Shijie <shijie8@gmail.com> wrote:
>
>
>> Minchan Kim a??e??:
>>
>>> On Mon, 20 Apr 2009 11:28:00 +0800
>>> Huang Shijie <shijie8@gmail.com> wrote:
>>>
>>> I will summarize your method.
>>> Is right ?
>>>
>>>
>>> kernel(driver) application
>>>
>>> posix_memalign(buffer)
>>> ioctl(buffer)
>>>
>>> ioctl handler
>>> get_user_pages(pages);
>>> /* This pages are mapped at user's vma'
>>> address space */
>>> vaddr = vmap(pages);
>>> /* This pages are mapped at vmalloc space */
>>> .
>>> .
>>> <after sometime,
>>> It may change to other process context>
>>> .
>>> .
>>> interrupt handler in your driver
>>> memcpy(vaddr, src, len);
>>> notify_user();
>>>
>>> processing(buffer);
>>>
>>> It's rather awkward use case of get_user_pages.
>>>
>>> If you want to share one big buffer between kernel and user,
>>> You can vmalloc and remap_pfn_range.
>>>
>>>
>> The v4l2 method IO_METHOD_MMAP does use the vmaloc() method you told above ,
>> our driver also support this method,we user vmalloc /remap_vmalloc_range().
>>
>> But the v4l2 method IO_METHOD_USERPTR must use the method I told above.
>>
>
> I can't understand IO_METHOD_USERPTR's benefit compared with IO_METHOD_MMAP.
> I think both solution can support that application programmer can handle buffer as like pointer and kernel can reduce copy overhead from kernel to user.
>
>
yes ,I agree with you .
But the application programmers do not know which method is more efficient.
> Why do you have to support IO_METHOD_USERPTR?
>
just for fun. For the v4l2 spec has the method ,why I don't realize it?
> If you can justify your goal, we can add locked GUP.
>
>
I can't .
--
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 prev parent reply other threads:[~2009-04-20 5:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 7:01 Does get_user_pages_fast lock the user pages in memory in my case? Huang Shijie
2009-04-18 6:18 ` KOSAKI Motohiro
2009-04-20 2:22 ` Huang Shijie
2009-04-19 23:45 ` Minchan Kim
2009-04-20 2:15 ` Huang Shijie
2009-04-20 2:42 ` Minchan Kim
2009-04-20 3:28 ` Huang Shijie
2009-04-20 3:42 ` KOSAKI Motohiro
2009-04-20 4:53 ` Minchan Kim
2009-04-20 5:05 ` KOSAKI Motohiro
2009-04-20 5:05 ` Huang Shijie
2009-04-20 5:19 ` KOSAKI Motohiro
2009-04-20 5:37 ` Huang Shijie
2009-04-20 7:59 ` KOSAKI Motohiro
2009-04-20 8:23 ` Huang Shijie
2009-04-20 9:24 ` KOSAKI Motohiro
2009-04-20 9:47 ` Huang Shijie
2009-04-21 1:43 ` KOSAKI Motohiro
2009-04-21 19:47 ` Christoph Lameter
2009-04-20 5:24 ` Minchan Kim
2009-04-20 5:42 ` Huang Shijie [this message]
2009-04-20 3:57 ` Huang Shijie
2009-04-22 6:08 ` Huang Shijie
2009-04-22 9:46 ` Minchan Kim
2009-04-20 3:18 ` KOSAKI Motohiro
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=49EC0B2A.5080600@gmail.com \
--to=shijie8@gmail.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@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 NNTP newsgroup(s).