From: Peter Xu <peterx@redhat.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alistair Popple <apopple@nvidia.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v2] mm: Avoid unnecessary page fault retires on shared memory types
Date: Wed, 18 May 2022 16:06:28 -0400 [thread overview]
Message-ID: <YoVRxLEHG392qsjR@xz-m1.local> (raw)
In-Reply-To: <20220506135205.46810-1-peterx@redhat.com>
On Fri, May 06, 2022 at 09:52:05AM -0400, Peter Xu wrote:
> v2:
> - Fix syzbot report
> - Added unit to the test results in commit message
>
> Note: I didn't copy any arch maintainers yet because I want to get some
> feedback from the mm people first.. I'll start doing so when there's a new
> version. Please have a look, thanks.
> ---
Any further comment on this one before I start to copy arch maintainers?
Thanks,
--
Peter Xu
prev parent reply other threads:[~2022-05-18 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:52 Peter Xu
2022-05-18 20:06 ` Peter Xu [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=YoVRxLEHG392qsjR@xz-m1.local \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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