From: Wu Fengguang <fengguang.wu@intel.com>
To: Ying Han <yinghan@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 02/14] mm: fix major/minor fault accounting on retried fault
Date: Wed, 8 Apr 2009 06:45:45 +0800 [thread overview]
Message-ID: <20090407224545.GA5607@localhost> (raw)
In-Reply-To: <604427e00904071258y78eea757m6d95d08deec49450@mail.gmail.com>
On Wed, Apr 08, 2009 at 03:58:16AM +0800, Ying Han wrote:
> On Tue, Apr 7, 2009 at 12:17 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
> > VM_FAULT_RETRY does make major/minor faults accounting a bit twisted..
> >
> > Cc: Ying Han <yinghan@google.com>
> > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> > ---
> > arch/x86/mm/fault.c | 2 ++
> > mm/memory.c | 22 ++++++++++++++--------
> > 2 files changed, 16 insertions(+), 8 deletions(-)
> >
> > --- mm.orig/arch/x86/mm/fault.c
> > +++ mm/arch/x86/mm/fault.c
> > @@ -1160,6 +1160,8 @@ good_area:
> > if (fault & VM_FAULT_RETRY) {
> > if (retry_flag) {
> > retry_flag = 0;
> > + tsk->maj_flt++;
> > + tsk->min_flt--;
> > goto retry;
> > }
> > BUG();
> sorry, little bit confuse here. are we assuming the retry path will
> return min_flt as always?
Sure - except for some really exceptional ftruncate cases.
The page was there ready, and we'll retry immediately.
maj_flt/min_flt are not _exact_ numbers by their nature, so 99.9%
accuracy shall be fine.
Thanks,
Fengguang
> > --- mm.orig/mm/memory.c
> > +++ mm/mm/memory.c
> > @@ -2882,26 +2882,32 @@ int handle_mm_fault(struct mm_struct *mm
> > pud_t *pud;
> > pmd_t *pmd;
> > pte_t *pte;
> > + int ret;
> >
> > __set_current_state(TASK_RUNNING);
> >
> > - count_vm_event(PGFAULT);
> > -
> > - if (unlikely(is_vm_hugetlb_page(vma)))
> > - return hugetlb_fault(mm, vma, address, write_access);
> > + if (unlikely(is_vm_hugetlb_page(vma))) {
> > + ret = hugetlb_fault(mm, vma, address, write_access);
> > + goto out;
> > + }
> >
> > + ret = VM_FAULT_OOM;
> > pgd = pgd_offset(mm, address);
> > pud = pud_alloc(mm, pgd, address);
> > if (!pud)
> > - return VM_FAULT_OOM;
> > + goto out;
> > pmd = pmd_alloc(mm, pud, address);
> > if (!pmd)
> > - return VM_FAULT_OOM;
> > + goto out;
> > pte = pte_alloc_map(mm, pmd, address);
> > if (!pte)
> > - return VM_FAULT_OOM;
> > + goto out;
> >
> > - return handle_pte_fault(mm, vma, address, pte, pmd, write_access);
> > + ret = handle_pte_fault(mm, vma, address, pte, pmd, write_access);
> > +out:
> > + if (!(ret & VM_FAULT_RETRY))
> > + count_vm_event(PGFAULT);
> > + return ret;
> > }
> >
> > #ifndef __PAGETABLE_PUD_FOLDED
> >
> > --
> >
> >
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: Ying Han <yinghan@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 02/14] mm: fix major/minor fault accounting on retried fault
Date: Wed, 8 Apr 2009 06:45:45 +0800 [thread overview]
Message-ID: <20090407224545.GA5607@localhost> (raw)
In-Reply-To: <604427e00904071258y78eea757m6d95d08deec49450@mail.gmail.com>
On Wed, Apr 08, 2009 at 03:58:16AM +0800, Ying Han wrote:
> On Tue, Apr 7, 2009 at 12:17 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
> > VM_FAULT_RETRY does make major/minor faults accounting a bit twisted..
> >
> > Cc: Ying Han <yinghan@google.com>
> > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> > ---
> > arch/x86/mm/fault.c | 2 ++
> > mm/memory.c | 22 ++++++++++++++--------
> > 2 files changed, 16 insertions(+), 8 deletions(-)
> >
> > --- mm.orig/arch/x86/mm/fault.c
> > +++ mm/arch/x86/mm/fault.c
> > @@ -1160,6 +1160,8 @@ good_area:
> > if (fault & VM_FAULT_RETRY) {
> > if (retry_flag) {
> > retry_flag = 0;
> > + tsk->maj_flt++;
> > + tsk->min_flt--;
> > goto retry;
> > }
> > BUG();
> sorry, little bit confuse here. are we assuming the retry path will
> return min_flt as always?
Sure - except for some really exceptional ftruncate cases.
The page was there ready, and we'll retry immediately.
maj_flt/min_flt are not _exact_ numbers by their nature, so 99.9%
accuracy shall be fine.
Thanks,
Fengguang
> > --- mm.orig/mm/memory.c
> > +++ mm/mm/memory.c
> > @@ -2882,26 +2882,32 @@ int handle_mm_fault(struct mm_struct *mm
> > pud_t *pud;
> > pmd_t *pmd;
> > pte_t *pte;
> > + int ret;
> >
> > __set_current_state(TASK_RUNNING);
> >
> > - count_vm_event(PGFAULT);
> > -
> > - if (unlikely(is_vm_hugetlb_page(vma)))
> > - return hugetlb_fault(mm, vma, address, write_access);
> > + if (unlikely(is_vm_hugetlb_page(vma))) {
> > + ret = hugetlb_fault(mm, vma, address, write_access);
> > + goto out;
> > + }
> >
> > + ret = VM_FAULT_OOM;
> > pgd = pgd_offset(mm, address);
> > pud = pud_alloc(mm, pgd, address);
> > if (!pud)
> > - return VM_FAULT_OOM;
> > + goto out;
> > pmd = pmd_alloc(mm, pud, address);
> > if (!pmd)
> > - return VM_FAULT_OOM;
> > + goto out;
> > pte = pte_alloc_map(mm, pmd, address);
> > if (!pte)
> > - return VM_FAULT_OOM;
> > + goto out;
> >
> > - return handle_pte_fault(mm, vma, address, pte, pmd, write_access);
> > + ret = handle_pte_fault(mm, vma, address, pte, pmd, write_access);
> > +out:
> > + if (!(ret & VM_FAULT_RETRY))
> > + count_vm_event(PGFAULT);
> > + return ret;
> > }
> >
> > #ifndef __PAGETABLE_PUD_FOLDED
> >
> > --
> >
> >
--
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>
next prev parent reply other threads:[~2009-04-07 22:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 7:17 [PATCH 00/14] filemap and readahead fixes Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 01/14] mm: fix find_lock_page_retry() return value parsing Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 02/14] mm: fix major/minor fault accounting on retried fault Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 19:58 ` Ying Han
2009-04-07 19:58 ` Ying Han
2009-04-07 19:58 ` Ying Han
2009-04-07 22:45 ` Wu Fengguang [this message]
2009-04-07 22:45 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 03/14] mm: remove FAULT_FLAG_RETRY dead code Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 20:03 ` Ying Han
2009-04-07 20:03 ` Ying Han
2009-04-07 23:27 ` Wu Fengguang
2009-04-07 23:27 ` Wu Fengguang
2009-04-08 1:17 ` Ying Han
2009-04-08 1:17 ` Ying Han
2009-04-08 2:29 ` Wu Fengguang
2009-04-08 2:29 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 04/14] mm: reduce duplicate page fault code Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 05/14] readahead: account mmap_miss for VM_FAULT_RETRY Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 06/14] readahead: move max_sane_readahead() calls into force_page_cache_readahead() Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 07/14] readahead: apply max_sane_readahead() limit in ondemand_readahead() Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 08/14] readahead: remove one unnecessary radix tree lookup Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 09/14] readahead: increase interleaved readahead size Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 10/14] readahead: remove sync/async readahead call dependency Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 11/14] readahead: clean up and simplify the code for filemap page fault readahead Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 12/14] readahead: sequential mmap readahead Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 13/14] readahead: enforce full readahead size on async " Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
2009-04-07 7:17 ` [PATCH 14/14] readahead: record mmap read-around states in file_ra_state Wu Fengguang
2009-04-07 7:17 ` Wu Fengguang
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 11:50 [PATCH 00/14] filemap and readahead fixes Wu Fengguang
2009-04-07 11:50 ` [PATCH 02/14] mm: fix major/minor fault accounting on retried fault Wu Fengguang
2009-04-07 11:50 ` Wu Fengguang
2009-04-07 11:50 ` Wu Fengguang
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=20090407224545.GA5607@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.