All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Peter Xu <peterx@redhat.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4] mm: Avoid unnecessary page fault retires on shared memory types
Date: Mon, 30 May 2022 14:04:12 +1000	[thread overview]
Message-ID: <87mtezll8j.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220527193936.30678-1-peterx@redhat.com>

Peter Xu <peterx@redhat.com> writes:
> I observed that for each of the shared file-backed page faults, we're very
> likely to retry one more time for the 1st write fault upon no page.  It's
> because we'll need to release the mmap lock for dirty rate limit purpose
> with balance_dirty_pages_ratelimited() (in fault_dirty_shared_page()).
>
...

>  arch/powerpc/mm/copro_fault.c |  5 +++++
>  arch/powerpc/mm/fault.c       |  5 +++++

Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)

cheers

  parent reply	other threads:[~2022-05-30  4:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 19:39 [PATCH v4] mm: Avoid unnecessary page fault retires on shared memory types Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-27 19:39 ` Peter Xu
2022-05-29 20:33 ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-29 20:33   ` Heiko Carstens
2022-05-30  9:35   ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30  9:35     ` Christian Borntraeger
2022-05-30 15:52     ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 15:52       ` Peter Xu
2022-05-30 16:00       ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 16:00         ` Peter Xu
2022-05-30 17:03         ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 17:03           ` Heiko Carstens
2022-05-30 18:29           ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29             ` Peter Xu
2022-05-30 18:29         ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30 18:29           ` Christian Borntraeger
2022-05-30  4:04 ` Michael Ellerman [this message]
2022-05-30 13:31 ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas
2022-05-30 13:31   ` Catalin Marinas

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=87mtezll8j.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=peterx@redhat.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.