linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: magnus.damm@gmail.com, linux-media@vger.kernel.org,
	hverkuil@xs4all.nl, lethal@linux-sh.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] mm: introduce follow_pte()
Date: Tue, 5 May 2009 14:05:17 -0700	[thread overview]
Message-ID: <20090505140517.bef78dd3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090505203807.GB2428@cmpxchg.org>

On Tue, 5 May 2009 22:38:07 +0200
Johannes Weiner <hannes@cmpxchg.org> wrote:

> On Tue, May 05, 2009 at 12:24:42PM -0700, Andrew Morton wrote:
> > On Mon,  4 May 2009 11:54:32 +0200
> > Johannes Weiner <hannes@cmpxchg.org> wrote:
> > 
> > > A generic readonly page table lookup helper to map an address space
> > > and an address from it to a pte.
> > 
> > umm, OK.
> > 
> > Is there actually some point to these three patches?  If so, what is it?
> 
> Magnus needs to check for physical contiguity of a VMAs backing pages
> to support zero-copy exportation of video data to userspace.
> 
> This series implements follow_pfn() so he can walk the VMA backing
> pages and ensure their PFNs are in linear order.
> 
> [ This patch can be collapsed with 2/3, I just thought it would be
>   easier to read the diffs when having them separate. ]
> 
> 1/3 and 2/3: factor out the page table walk from follow_phys() into
> follow_pte().
> 
> 3/3: implement follow_pfn() on top of follow_pte().

So we could bundle these patches with Magnus's patchset, or we could
consider these three patches as a cleanup or something.

Given that 3/3 introduces an unused function, I'm inclined to sit tight
and await Magnus's work.

--
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-05-05 21:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  9:01 [PATCH] videobuf-dma-contig: zero copy USERPTR support V2 Magnus Damm
2009-05-01  3:26 ` Magnus Damm
2009-05-01 18:14   ` Johannes Weiner
2009-05-04  9:54     ` [patch 1/3] mm: introduce follow_pte() Johannes Weiner
2009-05-05 19:24       ` Andrew Morton
2009-05-05 20:38         ` Johannes Weiner
2009-05-05 21:05           ` Andrew Morton [this message]
2009-05-05 21:21             ` Johannes Weiner
2009-05-08  8:51               ` Magnus Damm
2009-05-04  9:54     ` [patch 2/3] mm: use generic follow_pte() in follow_phys() Johannes Weiner
2009-05-04 10:08       ` Johannes Weiner
2009-05-04  9:54     ` [patch 3/3] mm: introduce follow_pfn() Johannes Weiner
2009-05-04 11:08       ` Christoph Hellwig
2009-05-04 13:13         ` [patch 3/3 v2] " Johannes Weiner
2009-05-04 14:31           ` Christoph Hellwig

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=20090505140517.bef78dd3.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=hverkuil@xs4all.nl \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=magnus.damm@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).