RE: [QUESTION] mmap of device file with huge pages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Dave Hansen [mailto:dave.hansen@xxxxxxxxx]
> Sent: Tuesday, August 09, 2016 20:40
> To: Yehuda Yitschak; linux-mm@xxxxxxxxx
> Cc: Shadi Ammouri
> Subject: Re: [QUESTION] mmap of device file with huge pages
> 
> On 08/09/2016 02:58 AM, Yehuda Yitschak wrote:
> > I would appreciate any advice on this issue
> 
> This is kinda a FAQ at this point.  

Sorry for posting a FAQ but I found nothing on the web.
There's tons of general material about mmap, huge-pages and device files but nothing on this specific use case.
I posted this question since I suspected I might need a ugly hack for this scenario.
Is there any standard solution to this issue ? 

> But, the thing I generally suggest is that you
> allocate hugetlbfs memory or anonymous transparent huge pages in your
> applciation via the _normal_ mechanisms, and then hand a pointer to that in
> to your driver.

Thanks. I can try that.
Once I hand the pointer to the driver, is there a standard API to map user-space memory to kernel space.

Thanks 

Yehuda 

> 
> It's backwards from how you're doing it now, but it makes things easier down
> the road.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]