All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Aug 7 (mm/khugepaged.c)
Date: Wed, 7 Aug 2019 22:13:33 +0000	[thread overview]
Message-ID: <4CB11692-DD66-4381-91DC-709C9B812B33@fb.com> (raw)
In-Reply-To: <20190807142755.8211d58d5ecec8082587b073@linux-foundation.org>



> On Aug 7, 2019, at 2:27 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> On Wed, 7 Aug 2019 21:00:04 +0000 Song Liu <songliubraving@fb.com> wrote:
> 
>>>> 
>>>> Shall I resend the patch, or shall I send fix on top of current patch?
>>> 
>>> Either is OK.  If the difference is small I will turn it into an
>>> incremental patch so that I (and others) can see what changed.
>> 
>> Please find the patch to fix this at the end of this email. It applies 
>> right on top of "khugepaged: enable collapse pmd for pte-mapped THP". 
>> It may conflict a little with the "Enable THP for text section of 
>> non-shmem files" set, which renames function khugepaged_scan_shmem(). 
>> 
>> Also, I found v3 of the set in linux-next. The latest is v4:
>> 
>> https://lkml.org/lkml/2019/8/2/1587
>> https://lkml.org/lkml/2019/8/2/1588
>> https://lkml.org/lkml/2019/8/2/1589
> 
> It's all a bit confusing.  I'll drop 

Agreed this is confusing. 

> 
> mm-move-memcmp_pages-and-pages_identical.patch
> uprobe-use-original-page-when-all-uprobes-are-removed.patch
> uprobe-use-original-page-when-all-uprobes-are-removed-v2.patch
> mm-thp-introduce-foll_split_pmd.patch
> mm-thp-introduce-foll_split_pmd-v11.patch
> uprobe-use-foll_split_pmd-instead-of-foll_split.patch
> khugepaged-enable-collapse-pmd-for-pte-mapped-thp.patch
> uprobe-collapse-thp-pmd-after-removing-all-uprobes.patch
> 
> Please resolve Oleg's review comments and resend everything.

Will do. 

Thanks,
Song

  parent reply	other threads:[~2019-08-07 22:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  8:36 linux-next: Tree for Aug 7 Stephen Rothwell
2019-08-07 15:11 ` linux-next: Tree for Aug 7 (mm/khugepaged.c) Randy Dunlap
2019-08-07 16:59   ` Song Liu
2019-08-07 20:10     ` Andrew Morton
2019-08-07 21:00       ` Song Liu
2019-08-07 21:27         ` Andrew Morton
2019-08-07 21:30           ` Randy Dunlap
2019-08-07 22:11             ` Song Liu
2019-08-08  1:31               ` Stephen Rothwell
2019-08-07 22:13           ` Song Liu [this message]
2019-08-08  1:20           ` Stephen Rothwell
2019-08-07 15:29 ` linux-next: Tree for Aug 7 (net/bridge/netfilter/nf_conntrack_bridge.c) Randy Dunlap
2019-08-07 15:29   ` [Bridge] " Randy Dunlap
2019-08-07 15:57   ` Jeremy Sowden
2019-08-07 15:57     ` [Bridge] " Jeremy Sowden
2019-09-23 22:26     ` Ivan Kalvachev
2019-09-23 22:26       ` [Bridge] " Ivan Kalvachev
2019-09-23 22:48       ` Jeremy Sowden
2019-09-23 22:48         ` [Bridge] " Jeremy Sowden
2019-08-08  5:13 ` linux-next: Tree for Aug 7 Michael Ellerman
2019-08-08 15:54   ` Gustavo A. R. Silva

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=4CB11692-DD66-4381-91DC-709C9B812B33@fb.com \
    --to=songliubraving@fb.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.