From: Yehuda Yitschak <yehuday@marvell.com>
To: Dave Hansen <dave.hansen@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Shadi Ammouri <shadi@marvell.com>
Subject: RE: [QUESTION] mmap of device file with huge pages
Date: Wed, 10 Aug 2016 07:36:29 +0000 [thread overview]
Message-ID: <ca84d8e02a0942c39ad0da01a1fe43f1@IL-EXCH02.marvell.com> (raw)
In-Reply-To: <57AA155B.70009@intel.com>
> -----Original Message-----
> From: Dave Hansen [mailto:dave.hansen@intel.com]
> Sent: Tuesday, August 09, 2016 20:40
> To: Yehuda Yitschak; linux-mm@kvack.org
> 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@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:[~2016-08-10 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 9:58 [QUESTION] mmap of device file with huge pages Yehuda Yitschak
2016-08-09 17:39 ` Dave Hansen
2016-08-10 7:36 ` Yehuda Yitschak [this message]
2016-08-10 16:20 ` Dave Hansen
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=ca84d8e02a0942c39ad0da01a1fe43f1@IL-EXCH02.marvell.com \
--to=yehuday@marvell.com \
--cc=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=shadi@marvell.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).