linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Zach O'Keefe" <zokeefe@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Hugh Dickins <hughd@google.com>,
	Yang Shi <shy828301@gmail.com>,
	 Miaohe Lin <linmiaohe@huawei.com>,
	"Zach O'Keefe" <zokeefe@google.com>
Subject: [PATCH mm-unstable 0/4] mm: fixes for userspace hugepage collapse, v7
Date: Wed, 20 Jul 2022 07:05:59 -0700	[thread overview]
Message-ID: <20220720140603.1958773-1-zokeefe@google.com> (raw)

Hey Andrew,

These are a few requested cleanups for the "mm: userspace hugepage collapse, v7"
series[1] currently in mm-unstable.  Please considering squashing them into the
v7 series.  Note that https://lkml.kernel.org/r/Ys4aTRqWIbjNs1mI@google.com is
still outstanding, and that the series is incomplete until a suitable resolution
is reached there.

Thanks, and apologies for the multiple fixes / adjustments required here.
Zach

[1] https://lore.kernel.org/linux-mm/20220706235936.2197195-1-zokeefe@google.com/


Zach O'Keefe (4):
  mm/khugepaged: Use minimal bits to store num page < HPAGE_PMD_NR
  mm/khugepaged: consistently order cc->is_khugepaged and pte_* checks
  mm/khugepaged: delay computation of hpage boundaries until use
  Revert "mm/madvise: add huge_memory:mm_madvise_collapse tracepoint"

 include/trace/events/huge_memory.h | 22 ----------
 mm/khugepaged.c                    | 64 +++++++++++++++++-------------
 2 files changed, 37 insertions(+), 49 deletions(-)

-- 
2.37.0.170.g444d1eabd0-goog



             reply	other threads:[~2022-07-20 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 14:05 Zach O'Keefe [this message]
2022-07-20 14:06 ` [PATCH mm-unstable 1/4] mm/khugepaged: Use minimal bits to store num page < HPAGE_PMD_NR Zach O'Keefe
2022-07-20 17:26   ` Yang Shi
2022-07-21  0:41   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 2/4] mm/khugepaged: consistently order cc->is_khugepaged and pte_* checks Zach O'Keefe
2022-07-20 17:27   ` Yang Shi
2022-07-20 19:09     ` Zach O'Keefe
2022-07-21  0:42   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 3/4] mm/khugepaged: delay computation of hpage boundaries until use Zach O'Keefe
2022-07-20 17:30   ` Yang Shi
2022-07-21  0:43   ` David Rientjes
2022-07-20 14:06 ` [PATCH mm-unstable 4/4] Revert "mm/madvise: add huge_memory:mm_madvise_collapse tracepoint" Zach O'Keefe
2022-07-20 17:30   ` Yang Shi
2022-07-21  0:43   ` David Rientjes

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=20220720140603.1958773-1-zokeefe@google.com \
    --to=zokeefe@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox