All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: aneesh.kumar@linux.vnet.ibm.com,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: A question about the patch(commit :c777e2a8b654 powerpc/mm: Fix Multi hit ERAT cause by recent THP update)
Date: Tue, 28 Jun 2016 10:35:08 +0800	[thread overview]
Message-ID: <5771E25C.10605@huawei.com> (raw)
In-Reply-To: <20160623093411.GB30077@dhcp22.suse.cz>

On 2016/6/23 17:34, Michal Hocko wrote:
> On Thu 23-06-16 11:29:46, Michal Hocko wrote:
>> On Wed 22-06-16 23:05:24, zhong jiang wrote:
>>> Hi  Aneesh
>>>
>>>                 CPU0                            CPU1
>>>     shrink_page_list()
>>>       add_to_swap()
>>>         split_huge_page_to_list()
>>>           __split_huge_pmd_locked()
>>>             pmdp_huge_clear_flush_notify()
>>>         // pmd_none() == true
>>>                                         exit_mmap()
>>>                                           unmap_vmas()
>>>                                             zap_pmd_range()
>>>                                               // no action on pmd since pmd_none() == true
>>>         pmd_populate()
>>>
>>>
>>> the mm should be the last user  when CPU1 process is exiting,  CPU0 must be a own mm .
>>> two different process  should not be influenced each other.  in a words , they should not
>>> have race.
>> No this is a different scenario than
>> http://lkml.kernel.org/r/1466517956-13875-1-git-send-email-zhongjiang@huawei.com
>> we were discussing recently. Note that pages are still on the LRU lists
>> while the mm which maps them is exiting. So the above race is very much
>> possible.
> And just to clarify, I haven't checked the current code after c777e2a8b654
> ("powerpc/mm: Fix Multi hit ERAT cause by recent THP update") which is
> ppc specific and I have no idea whether other arches need a similar
> treatment. I was merely trying to explain that the mm exclusive argument
> doesn't apply to reclaim vs. exit races.
  Thank for your explaintion!

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2016-06-28  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:05 A question about the patch(commit :c777e2a8b654 powerpc/mm: Fix Multi hit ERAT cause by recent THP update) zhong jiang
2016-06-23  9:29 ` Michal Hocko
2016-06-23  9:34   ` Michal Hocko
2016-06-28  2:35     ` zhong jiang [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=5771E25C.10605@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.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 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.