linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
	Rik van Riel <riel@redhat.com>,
	David Rientjes <rientjes@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH] mm: Fix the TLB range flushed when __tlb_remove_page() runs out of slots
Date: Wed, 29 May 2013 19:38:37 +0530	[thread overview]
Message-ID: <51A60BE5.7010905@synopsys.com> (raw)
In-Reply-To: <20130529140319.GK17767@MacBook-Pro.local>

On 05/29/2013 07:33 PM, Catalin Marinas wrote:
> On Wed, May 29, 2013 at 01:56:13PM +0100, Vineet Gupta wrote:
>> zap_pte_range loops from @addr to @end. In the middle, if it runs out of
>> batching slots, TLB entries needs to be flushed for @start to @interim,
>> NOT @interim to @end.
>>
>> Since ARC port doesn't use page free batching I can't test it myself but
>> this seems like the right thing to do.
>> Observed this when working on a fix for the issue at thread:
>> 	http://www.spinics.net/lists/linux-arch/msg21736.html
>>
>> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Mel Gorman <mgorman@suse.de>
>> Cc: Hugh Dickins <hughd@google.com>
>> Cc: Rik van Riel <riel@redhat.com>
>> Cc: David Rientjes <rientjes@google.com>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Cc: linux-mm@kvack.org
>> Cc: linux-arch@vger.kernel.org <linux-arch@vger.kernel.org>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Max Filippov <jcmvbkbc@gmail.com>
>> ---
>>  mm/memory.c |    9 ++++++---
>>  1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/memory.c b/mm/memory.c
>> index 6dc1882..d9d5fd9 100644
>> --- a/mm/memory.c
>> +++ b/mm/memory.c
>> @@ -1110,6 +1110,7 @@ static unsigned long zap_pte_range(struct mmu_gather *tlb,
>>  	spinlock_t *ptl;
>>  	pte_t *start_pte;
>>  	pte_t *pte;
>> +	unsigned long range_start = addr;
>>  
>>  again:
>>  	init_rss_vec(rss);
>> @@ -1215,12 +1216,14 @@ again:
>>  		force_flush = 0;
>>  
>>  #ifdef HAVE_GENERIC_MMU_GATHER
>> -		tlb->start = addr;
>> -		tlb->end = end;
>> +		tlb->start = range_start;
>> +		tlb->end = addr;
>>  #endif
>>  		tlb_flush_mmu(tlb);
>> -		if (addr != end)
>> +		if (addr != end) {
>> +			range_start = addr;
>>  			goto again;
>> +		}
>>  	}
> Isn't this code only run if force_flush != 0? force_flush is set to
> !__tlb_remove_page() and this function always returns 1 on (generic TLB)
> UP since tlb_fast_mode() is 1. There is no batching on UP with the
> generic TLB code.

Correct ! That's why the changelog says I couldn't test it on ARC port itself :-)

However based on the other discussion (Max's TLB/PTE inconsistency), as I started
writing code to reuse this block to flush the TLB even for non forced case, I
realized that what this is doing is incorrect and won't work for the general flushing.

Ignoring all other threads, do we agree that the exiting code - if used in any
situations is incorrect semantically ?

-Vineet

--
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:[~2013-05-29 14:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 12:56 [PATCH] mm: Fix the TLB range flushed when __tlb_remove_page() runs out of slots Vineet Gupta
2013-05-29 14:03 ` Catalin Marinas
2013-05-29 14:08   ` Vineet Gupta [this message]
2013-05-29 14:29     ` Catalin Marinas
2013-05-29 14:36       ` Vineet Gupta
2013-05-29 14:51         ` Catalin Marinas
2013-05-30  5:02 ` Vineet Gupta
2013-07-29 23:41 ` David Miller
2013-07-29 23:46   ` Andrew Morton
2013-07-30  0:16     ` Greg KH

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=51A60BE5.7010905@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=hughd@google.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).