From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-mm@kvack.org, linux-arch@vger.kernel.org
Subject: [PATCH] Comments about superflous flush_tlb_range calls.
Date: Fri, 21 Nov 2003 18:49:47 +0100 [thread overview]
Message-ID: <20031121174947.GE1341@mschwid3.boeblingen.de.ibm.com> (raw)
Hi,
while searching for a s390 tlb flush problem I noticed some superflous
tlb flushes. One in zeromap_page_range, one in remap_page_range, and
another one in filemap_sync. The patch just adds comments but I think
these three flush_tlb_range calls can be removed.
blue skies,
Martin.
diffstat:
mm/memory.c | 6 ++++++
mm/msync.c | 4 ++++
2 files changed, 10 insertions(+)
diff -urN linux-2.6/mm/memory.c linux-2.6-s390/mm/memory.c
--- linux-2.6/mm/memory.c Fri Nov 21 16:18:48 2003
+++ linux-2.6-s390/mm/memory.c Fri Nov 21 16:20:25 2003
@@ -863,6 +863,9 @@
address = (address + PGDIR_SIZE) & PGDIR_MASK;
dir++;
} while (address && (address < end));
+ /*
+ * Why flush? zeromap_pte_range has a BUG_ON for !pte_none()
+ */
flush_tlb_range(vma, beg, end);
spin_unlock(&mm->page_table_lock);
return error;
@@ -944,6 +947,9 @@
from = (from + PGDIR_SIZE) & PGDIR_MASK;
dir++;
} while (from && (from < end));
+ /*
+ * Why flush? remap_pte_range has a BUG_ON for !pte_none()
+ */
flush_tlb_range(vma, beg, end);
spin_unlock(&mm->page_table_lock);
return error;
diff -urN linux-2.6/mm/msync.c linux-2.6-s390/mm/msync.c
--- linux-2.6/mm/msync.c Sat Oct 25 20:43:26 2003
+++ linux-2.6-s390/mm/msync.c Fri Nov 21 16:20:25 2003
@@ -115,6 +115,10 @@
address = (address + PGDIR_SIZE) & PGDIR_MASK;
dir++;
} while (address && (address < end));
+ /*
+ * Why flush ? filemap_sync_pte already flushed the tlbs with the
+ * dirty bits.
+ */
flush_tlb_range(vma, end - size, end);
spin_unlock(&vma->vm_mm->page_table_lock);
--
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:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2003-11-21 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031121174947.GE1341@mschwid3.boeblingen.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.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