All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 2/3] powerpc/mm: Implement pmdp_establish for ppc64
Date: Thu, 27 Jul 2017 21:22:55 +0530	[thread overview]
Message-ID: <1cd105a8-5d07-0768-867c-54e678f5f828@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170727125644.GC27766@dhcp22.suse.cz>



On 07/27/2017 06:26 PM, Michal Hocko wrote:
> On Thu 27-07-17 14:07:55, Aneesh Kumar K.V wrote:
>> We can now use this to set pmd page table entries to absolute values. THP
>> need to ensure that we always update pmd PTE entries such that we never mark
>> the pmd none. pmdp_establish helps in implementing that.
>>
>> This doesn't flush the tlb. Based on the old_pmd value returned caller can
>> decide to call flush_pmd_tlb_range()
> 
> _Why_ do we need this. It doesn't really help that the newly added
> function is not used so we could check that...


We were looking at having pmdp_establish used by the core code. But i 
guess Kirill ended up using pmdp_invalidate. If we don't have 
pmdp_establish usage in core code, we can drop this. This is to help 
Kiril make progress with series at


https://lkml.kernel.org/r/20170615145224.66200-1-kirill.shutemov@linux.intel.com


Also thinking about the interface further, I guess pmdp_establish 
interface is some what confusing. So we may want to rethink this 
further. I know that i asked for pmdp_establish in earlier review of 
Kirill's patchset. But now looking back i am not sure we can clearly 
explain only semantic requirement of pmdp_establish. One thing we may 
want to clarify is whether we should retain the Reference and change bit 
from the old entry when we are doing a pmdp_establish ?

Kirill,

Considering core code is still only using pmdp_invalidate(), we may want 
to drop this interface completely ?

-aneesh

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 2/3] powerpc/mm: Implement pmdp_establish for ppc64
Date: Thu, 27 Jul 2017 21:22:55 +0530	[thread overview]
Message-ID: <1cd105a8-5d07-0768-867c-54e678f5f828@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170727125644.GC27766@dhcp22.suse.cz>



On 07/27/2017 06:26 PM, Michal Hocko wrote:
> On Thu 27-07-17 14:07:55, Aneesh Kumar K.V wrote:
>> We can now use this to set pmd page table entries to absolute values. THP
>> need to ensure that we always update pmd PTE entries such that we never mark
>> the pmd none. pmdp_establish helps in implementing that.
>>
>> This doesn't flush the tlb. Based on the old_pmd value returned caller can
>> decide to call flush_pmd_tlb_range()
> 
> _Why_ do we need this. It doesn't really help that the newly added
> function is not used so we could check that...


We were looking at having pmdp_establish used by the core code. But i 
guess Kirill ended up using pmdp_invalidate. If we don't have 
pmdp_establish usage in core code, we can drop this. This is to help 
Kiril make progress with series at


https://lkml.kernel.org/r/20170615145224.66200-1-kirill.shutemov@linux.intel.com


Also thinking about the interface further, I guess pmdp_establish 
interface is some what confusing. So we may want to rethink this 
further. I know that i asked for pmdp_establish in earlier review of 
Kirill's patchset. But now looking back i am not sure we can clearly 
explain only semantic requirement of pmdp_establish. One thing we may 
want to clarify is whether we should retain the Reference and change bit 
from the old entry when we are doing a pmdp_establish ?

Kirill,

Considering core code is still only using pmdp_invalidate(), we may want 
to drop this interface completely ?

-aneesh

  reply	other threads:[~2017-07-27 15:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  8:37 [RFC PATCH 1/3] powerpc/mm: update pmdp_invalidate to return old pmd value Aneesh Kumar K.V
2017-07-27  8:37 ` Aneesh Kumar K.V
2017-07-27  8:37 ` [RFC PATCH 2/3] powerpc/mm: Implement pmdp_establish for ppc64 Aneesh Kumar K.V
2017-07-27  8:37   ` Aneesh Kumar K.V
2017-07-27 12:56   ` Michal Hocko
2017-07-27 12:56     ` Michal Hocko
2017-07-27 15:52     ` Aneesh Kumar K.V [this message]
2017-07-27 15:52       ` Aneesh Kumar K.V
2017-07-27  8:37 ` [RFC PATCH 3/3] mm/hugetlb: Remove pmd_huge_split_prepare Aneesh Kumar K.V
2017-07-27  8:37   ` Aneesh Kumar K.V
2017-07-27 10:50   ` Aneesh Kumar K.V
2017-07-27 10:50     ` Aneesh Kumar K.V
2017-07-27 12:57   ` Michal Hocko
2017-07-27 12:57     ` Michal Hocko
2017-07-27 15:57     ` Aneesh Kumar K.V
2017-07-27 15:57       ` Aneesh Kumar K.V
2017-07-28  7:04       ` Michal Hocko
2017-07-28  7:04         ` Michal Hocko
2017-07-27 12:54 ` [RFC PATCH 1/3] powerpc/mm: update pmdp_invalidate to return old pmd value Michal Hocko
2017-07-27 12:54   ` Michal Hocko
2017-07-27 12:58   ` Kirill A. Shutemov
2017-07-27 12:58     ` Kirill A. Shutemov
2017-07-27 15:48   ` Aneesh Kumar K.V
2017-07-27 15:48     ` Aneesh Kumar K.V
2017-07-28  7:01     ` Michal Hocko
2017-07-28  7:01       ` Michal Hocko

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=1cd105a8-5d07-0768-867c-54e678f5f828@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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.