linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Gerald Schaefer <gerald.schaefer@de.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Will Deacon <will@kernel.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	David Rientjes <rientjes@google.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH v5 18/25] mm/s390: Use general page fault accounting
Date: Wed, 8 Jul 2020 10:30:54 -0400	[thread overview]
Message-ID: <20200708143054.GB199122@xz-x1> (raw)
In-Reply-To: <20200708054947.GA4026@oc3871087118.ibm.com>

On Wed, Jul 08, 2020 at 07:49:47AM +0200, Alexander Gordeev wrote:
> On Tue, Jul 07, 2020 at 06:50:14PM -0400, Peter Xu wrote:
> > Use the general page fault accounting by passing regs into handle_mm_fault().
> > It naturally solve the issue of multiple page fault accounting when page fault
> > retry happened.
> > 
> > CC: Heiko Carstens <heiko.carstens@de.ibm.com>
> > CC: Vasily Gorbik <gor@linux.ibm.com>
> > CC: Christian Borntraeger <borntraeger@de.ibm.com>
> > CC: linux-s390@vger.kernel.org
> > Reviewed-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
> > Acked-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> >  arch/s390/mm/fault.c | 16 +---------------
> >  1 file changed, 1 insertion(+), 15 deletions(-)
> > 
> > diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
> > index fc14df0b4d6e..9aa201df2e94 100644
> > --- a/arch/s390/mm/fault.c
> > +++ b/arch/s390/mm/fault.c
> > @@ -478,7 +478,7 @@ static inline vm_fault_t do_exception(struct pt_regs *regs, int access)
> >  	 * make sure we exit gracefully rather than endlessly redo
> >  	 * the fault.
> >  	 */
> > -	fault = handle_mm_fault(vma, address, flags, NULL);
> > +	fault = handle_mm_fault(vma, address, flags, regs);
> >  	if (fault_signal_pending(fault, regs)) {
> >  		fault = VM_FAULT_SIGNAL;
> >  		if (flags & FAULT_FLAG_RETRY_NOWAIT)
> > @@ -488,21 +488,7 @@ static inline vm_fault_t do_exception(struct pt_regs *regs, int access)
> >  	if (unlikely(fault & VM_FAULT_ERROR))
> >  		goto out_up;
> >  
> > -	/*
> > -	 * Major/minor page fault accounting is only done on the
> > -	 * initial attempt. If we go through a retry, it is extremely
> > -	 * likely that the page will be found in page cache at that point.
> > -	 */
> >  	if (flags & FAULT_FLAG_ALLOW_RETRY) {
> 
> Shouldn't this check ^^^ be dropped as well?
> 
> Since commit 4064b9827063 ("mm: allow VM_FAULT_RETRY for multiple times")
> FAULT_FLAG_ALLOW_RETRY never gets unset, so no need to check..

I agree, but it should be out of the scope of the accounting changes that this
patch wants to address.  Maybe more suitable for a work on top?

This should also exist for most of the archs too, and I'm also not sure whether
compiler could be smart enough to optimize this directly since it seems to have
all the knowledge.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2020-07-08 14:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 22:49 [PATCH v5 00/25] mm: Page fault accounting cleanups Peter Xu
2020-07-07 22:49 ` [PATCH v5 01/25] mm: Do page fault accounting in handle_mm_fault Peter Xu
2020-07-07 22:49 ` [PATCH v5 02/25] mm/alpha: Use general page fault accounting Peter Xu
2020-07-07 22:49 ` [PATCH v5 03/25] mm/arc: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 04/25] mm/arm: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 05/25] mm/arm64: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 06/25] mm/csky: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 07/25] mm/hexagon: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 08/25] mm/ia64: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 09/25] mm/m68k: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 10/25] mm/microblaze: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 11/25] mm/mips: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 12/25] mm/nds32: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 13/25] mm/nios2: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 14/25] mm/openrisc: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 15/25] mm/parisc: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 16/25] mm/powerpc: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 17/25] mm/riscv: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 18/25] mm/s390: " Peter Xu
2020-07-08  5:49   ` Alexander Gordeev
2020-07-08 14:30     ` Peter Xu [this message]
2020-07-07 22:50 ` [PATCH v5 19/25] mm/sh: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 20/25] mm/sparc32: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 21/25] mm/sparc64: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 22/25] mm/x86: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 23/25] mm/xtensa: " Peter Xu
2020-07-07 22:50 ` [PATCH v5 24/25] mm: Clean up the last pieces of page fault accountings Peter Xu
2020-07-07 22:50 ` [PATCH v5 25/25] mm/gup: Remove task_struct pointer for all gup code Peter Xu

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=20200708143054.GB199122@xz-x1 \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@de.ibm.com \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox