linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>,
	linux-mm@kvack.org, Tony Luck <tony.luck@intel.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	nao.horiguchi@gmail.com, Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Muchun Song <muchun.song@linux.dev>,
	Benjamin LaHaise <bcrl@kvack.org>,
	jglisse@redhat.com, Jiaqi Yan <jiaqiyan@google.com>,
	Hugh Dickins <hughd@google.com>,
	Vishal Moola <vishal.moola@gmail.com>,
	Alistair Popple <apopple@nvidia.com>,
	Oscar Salvador <osalvador@suse.de>,
	Lance Yang <ioworker0@gmail.com>
Subject: Re: [PATCH v4 2/6] mm: add folio_mc_copy()
Date: Tue, 4 Jun 2024 20:31:25 -0700	[thread overview]
Message-ID: <20240604203125.3de9820af6a1637b0ad578b4@linux-foundation.org> (raw)
In-Reply-To: <51a26c6d-7614-42c7-aaa6-9a00d7cdc535@oracle.com>

On Tue, 4 Jun 2024 12:41:20 -0700 Jane Chu <jane.chu@oracle.com> wrote:

> >   int sysctl_overcommit_memory __read_mostly = OVERCOMMIT_GUESS;
> >   int sysctl_overcommit_ratio __read_mostly = 50;
> >   unsigned long sysctl_overcommit_kbytes __read_mostly;
> 
> Reviewed-by: Jane Chu <jane.chu@oracle.com>

Thanks.  I'll merge the series for testing, but I'd prefer to see more
review activity before proceeding further.  Please.



  reply	other threads:[~2024-06-05  3:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  9:24 [PATCH v4 0/6] mm: migrate: support poison recover from migrate folio Kefeng Wang
2024-06-03  9:24 ` [PATCH v4 1/6] mm: move memory_failure_queue() into copy_mc_[user]_highpage() Kefeng Wang
2024-06-04 19:38   ` Jane Chu
2024-06-06  2:28   ` Miaohe Lin
2024-06-03  9:24 ` [PATCH v4 2/6] mm: add folio_mc_copy() Kefeng Wang
2024-06-04 19:41   ` Jane Chu
2024-06-05  3:31     ` Andrew Morton [this message]
2024-06-05  7:15       ` Kefeng Wang
2024-06-06  2:36   ` Miaohe Lin
2024-06-03  9:24 ` [PATCH v4 3/6] mm: migrate: split folio_migrate_mapping() Kefeng Wang
2024-06-06  0:54   ` Jane Chu
2024-06-06  1:24     ` Kefeng Wang
2024-06-06  1:55       ` Matthew Wilcox
2024-06-06  2:24         ` Kefeng Wang
2024-06-06 18:28   ` Jane Chu
2024-06-03  9:24 ` [PATCH v4 4/6] mm: migrate: support poisoned recover from migrate folio Kefeng Wang
2024-06-06 21:27   ` Jane Chu
2024-06-06 22:28     ` Jane Chu
2024-06-06 22:31       ` Jane Chu
2024-06-07  4:01         ` Kefeng Wang
2024-06-07 15:59           ` Jane Chu
2024-06-03  9:24 ` [PATCH v4 5/6] fs: hugetlbfs: support poison recover from hugetlbfs_migrate_folio() Kefeng Wang
2024-06-06 23:30   ` Jane Chu
2024-06-03  9:24 ` [PATCH v4 6/6] mm: migrate: remove folio_migrate_copy() Kefeng Wang
2024-06-06 23:46   ` Jane Chu

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=20240604203125.3de9820af6a1637b0ad578b4@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=bcrl@kvack.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=ioworker0@gmail.com \
    --cc=jane.chu@oracle.com \
    --cc=jglisse@redhat.com \
    --cc=jiaqiyan@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=tony.luck@intel.com \
    --cc=vishal.moola@gmail.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.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