From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH] extend prefault helpers to fault in more than PAGE_SIZE
Date: Thu, 16 Feb 2012 13:01:35 +0100 [thread overview]
Message-ID: <1329393696-4802-1-git-send-email-daniel.vetter@ffwll.ch> (raw)
Hi all,
drm/i915 has write/read paths to upload/download data to/from gpu buffer
objects. For a bunch of reasons we have special fastpaths with decent setup
costs, so when we fall back to the slow-path we don't fully recover to the
fastest fast-path when grabbing our locks again. This is also in parts due to
that we have multiple fallbacks to slower paths, so control-flow in our code
would get really ugly.
As part of a larger rewrite and re-tuning of these functions we've noticed that
the prefault helpers in pagemap.h only prefault up to PAGE_SIZE because that's
all the other users need. The follow-up patch extends this to abritary sizes so
that we can fully exploit our special fastpaths in more cases (we typically see
reads and writes of a few pages up to a few mb).
I'd like to get this in for 3.4. There's no functional dependency between this
patch and the drm/i915 rework (only performance effects), so this can go in
through -mm without causing merge issues.
If this or something similar isn't acceptable, plan B is to hand-roll these 2
functions in drm/i915. But I don't like nih these things in driver code much.
Comments highly welcome.
Yours, Daniel
For reference, the drm/i915 read/write rework is avaialable at:
http://cgit.freedesktop.org/~danvet/drm/log/?h=pwrite-pread
Unfortunately cgit.fd.o is currently on hiatus.
Daniel Vetter (1):
mm: extend prefault helpers to fault in more than PAGE_SIZE
include/linux/pagemap.h | 28 ++++++++++++++++++----------
1 files changed, 18 insertions(+), 10 deletions(-)
--
1.7.7.5
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-02-16 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:01 Daniel Vetter [this message]
2012-02-16 12:01 ` [PATCH] mm: " Daniel Vetter
2012-02-16 13:32 ` Hillf Danton
2012-02-16 15:14 ` Daniel Vetter
2012-02-17 13:06 ` Hillf Danton
2012-02-23 22:36 ` Andrew Morton
2012-02-24 13:34 ` Daniel Vetter
2012-02-24 20:40 ` Andrew Morton
2012-02-29 14:03 ` Daniel Vetter
2012-02-29 23:01 ` Andrew Morton
2012-02-29 23:14 ` Daniel Vetter
2012-02-29 23:32 ` Andrew Morton
2012-03-01 19:22 ` Daniel Vetter
2012-03-01 20:15 ` Andrew Morton
2012-03-27 11:37 ` Daniel Vetter
2012-04-13 19:12 ` Geert Uytterhoeven
2012-04-14 16:03 ` [PATCH] mm: fixup compilation error due to an asm write through a const pointer Daniel Vetter
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=1329393696-4802-1-git-send-email-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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