From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: david@redhat.com
Cc: mhocko@kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
gregkh@linuxfoundation.org, mingo@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
dan.j.williams@intel.com, jack@suse.cz, mawilcox@microsoft.com,
jglisse@redhat.com, Souptick Joarder <jrdr.linux@gmail.com>,
kirill.shutemov@linux.intel.com, Vlastimil Babka <vbabka@suse.cz>,
osalvador@techadventures.net, yasu.isimatu@gmail.com,
malat@debian.org, Mel Gorman <mgorman@suse.de>,
iamjoonsoo.kim@lge.com
Subject: Re: [PATCH v1] mm: inititalize struct pages when adding a section
Date: Mon, 30 Jul 2018 11:45:31 -0400 [thread overview]
Message-ID: <CAGM2rebjVFpeWKV1wx5=3f6=Tx6h5qT9jszacGpB9pEcYKO1FA@mail.gmail.com> (raw)
In-Reply-To: <0be90c23-e5a0-2628-c671-9923d8e45b0a@redhat.com>
>
> So i guess we agree that the right fix for this is to not touch struct
> pages when removing memory, correct?
Yes in my opinion that would be the correct fix.
Thank you,
Pavel
>
> --
>
> Thanks,
>
> David / dhildenb
>
prev parent reply other threads:[~2018-07-30 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:54 David Hildenbrand
2018-07-27 17:25 ` Pavel Tatashin
2018-07-27 18:01 ` David Hildenbrand
2018-07-30 11:30 ` Michal Hocko
2018-07-30 11:53 ` David Hildenbrand
2018-07-30 12:05 ` Michal Hocko
2018-07-30 12:11 ` David Hildenbrand
2018-07-30 13:30 ` Pavel Tatashin
2018-07-30 13:51 ` David Hildenbrand
2018-07-30 14:10 ` Michal Hocko
2018-07-30 14:42 ` David Hildenbrand
2018-07-30 14:50 ` Michal Hocko
2018-07-30 15:03 ` David Hildenbrand
2018-07-30 15:45 ` Pavel Tatashin [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='CAGM2rebjVFpeWKV1wx5=3f6=Tx6h5qT9jszacGpB9pEcYKO1FA@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=mawilcox@microsoft.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=osalvador@techadventures.net \
--cc=vbabka@suse.cz \
--cc=yasu.isimatu@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