linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Korolev <akorolev@infradead.org>
To: Mel Gorman <mel@csn.ul.ie>, linux-mm@kvack.org
Subject: [RFC][PATCH 0/2] HugeTLB mapping for drivers
Date: Mon, 13 Jul 2009 23:17:48 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907132312550.25576@casper.infradead.org> (raw)

Hi,

The patch listed below provides device drivers with possibility to map
memory regions to user mode via HTLB interfaces.

This post is continuation of the topic being discussed here
http://marc.info/?l=linux-mm&m=124478168514639&w=2 . 
Thanks to Mel who gave good advice and code prototype. Couple weeks were
spent to understand how hugetlb works and initial version of the patch
is done. 

Why we need it? It is a common practice for device drivers to map memory
regions to user-space to allow data handling in user mode. (There are
plenty of examples in driver folder). Involving hugetlb mapping may
bring performance gain if mapped region is relatively large. Our tests
showed that it is possible to gain up to 7% performance gain if htlb
mapping is enabled. In my case involving hugetlb starts to make sense if
buffer is more or equal to 4MB. Since devices throughput grow up there
are more and more reasons to involve huge pages to remap very large mem regions.

The following messages contain patch and a simple driver example.
Patch has early revision. There are many doubtful places. Your critics
and suggestions are welocme.

Thanks,
Alexey

--
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:[~2009-07-13 21:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.00.0907132312550.25576@casper.infradead.org \
    --to=akorolev@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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