All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
	"walken@google.com" <walken@google.com>,
	"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"nickpiggin@yahoo.com.au" <nickpiggin@yahoo.com.au>,
	"riel@redhat.com" <riel@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"yinghan@google.com" <yinghan@google.com>
Subject: Re: + mm-retry-page-fault-when-blocking-on-disk-transfer.patch added to -mm tree
Date: Wed, 6 Oct 2010 10:46:05 +0800	[thread overview]
Message-ID: <20101006024605.GC8454@localhost> (raw)
In-Reply-To: <201010052015.o95KFP1G017428@imap1.linux-foundation.org>

On Wed, Oct 06, 2010 at 04:15:25AM +0800, Andrew Morton wrote:
> 
> The patch titled
>      mm: retry page fault when blocking on disk transfer
> has been added to the -mm tree.  Its filename is
>      mm-retry-page-fault-when-blocking-on-disk-transfer.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 
> See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> out what to do about this
> 
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> 
> ------------------------------------------------------
> Subject: mm: retry page fault when blocking on disk transfer
> From: Michel Lespinasse <walken@google.com>
> 
> This change reduces mmap_sem hold times that are caused by waiting for
> disk transfers when accessing file mapped VMAs.
> 
> It introduces the VM_FAULT_ALLOW_RETRY flag, which indicates that the call
> site wants mmap_sem to be released if blocking on a pending disk transfer.
>  In that case, filemap_fault() returns the VM_FAULT_RETRY status bit and
> do_page_fault() will then re-acquire mmap_sem and retry the page fault.
> 
> It is expected that the retry will hit the same page which will now be
> cached, and thus it will complete with a low mmap_sem hold time.
> 
> Signed-off-by: Michel Lespinasse <walken@google.com>
> Acked-by: Rik van Riel <riel@redhat.com>

Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>

Also would like to see Ying Han's Signed-off-by :)

Thanks,
Fengguang

      reply	other threads:[~2010-10-06  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 20:15 + mm-retry-page-fault-when-blocking-on-disk-transfer.patch added to -mm tree akpm
2010-10-06  2:46 ` Wu Fengguang [this message]

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=20101006024605.GC8454@localhost \
    --to=fengguang.wu@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@google.com \
    --cc=yinghan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.