All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Shaohua Li <shli@kernel.org>
Cc: linux-mm@kvack.org, fengguang.wu@intel.com, akpm@linux-foundation.org
Subject: Re: [patch]readahead: fault retry breaks mmap file read random detection
Date: Wed, 22 Aug 2012 11:40:33 -0400	[thread overview]
Message-ID: <5034FD71.3000406@redhat.com> (raw)
In-Reply-To: <20120822034012.GA24099@kernel.org>

On 08/21/2012 11:40 PM, Shaohua Li wrote:
> .fault now can retry. The retry can break state machine of .fault. In
> filemap_fault, if page is miss, ra->mmap_miss is increased. In the second try,
> since the page is in page cache now, ra->mmap_miss is decreased. And these are
> done in one fault, so we can't detect random mmap file access.
>
> Add a new flag to indicate .fault is tried once. In the second try, skip
> ra->mmap_miss decreasing. The filemap_fault state machine is ok with it.

> Index: linux/arch/avr32/mm/fault.c
> ===================================================================
> --- linux.orig/arch/avr32/mm/fault.c	2012-08-22 09:51:23.035526683 +0800
> +++ linux/arch/avr32/mm/fault.c	2012-08-22 09:52:22.822775020 +0800
> @@ -152,6 +152,7 @@ good_area:
>   			tsk->min_flt++;
>   		if (fault & VM_FAULT_RETRY) {
>   			flags &= ~FAULT_FLAG_ALLOW_RETRY;
> +			flags |= FAULT_FLAG_TRIED;

Is there any place where you set FAULT_FLAG_TRIED
where FAULT_FLAG_ALLOW_RETRY is not cleared?

In other words, could we use the absence of the
FAULT_FLAG_ALLOW_RETRY as the test, avoiding the
need for a new bit flag?

--
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:[~2012-08-22 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  3:40 [patch]readahead: fault retry breaks mmap file read random detection Shaohua Li
2012-08-22 15:40 ` Rik van Riel [this message]
2012-08-23  1:10   ` Shaohua Li
2012-08-30 17:21     ` Minchan Kim

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=5034FD71.3000406@redhat.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=shli@kernel.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 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.