public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [patch 07/10] Optimize storage key handling for anonymous pages
Date: Fri, 16 Nov 2007 15:24:48 +0100	[thread overview]
Message-ID: <20071116142527.252876230@de.ibm.com> (raw)
In-Reply-To: 20071116142441.484714036@de.ibm.com

[-- Attachment #1: 007-dirty-bit.diff --]
[-- Type: text/plain, Size: 1601 bytes --]

From: Christian Borntraeger <borntraeger@de.ibm.com>

page_mkclean used to call page_clear_dirty for every given page. This
is different to all other architectures, where the dirty bit in the
PTEs is only resetted, if page_mapping() returns a non-NULL pointer.
We can move the page_test_dirty/page_clear_dirty sequence into the 
2nd if to avoid unnecessary iske/sske sequences, which are expensive.

This change also helps kvm for s390 as the host must transfer the 
dirty bit into the guest status bits. By moving the page_clear_dirty
operation into the 2nd if, the vm will only call page_clear_dirty
for pages where it walks the mapping anyway. There it calls
ptep_clear_flush for writable ptes, so we can transfer the dirty bit
to the guest. 

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
---

 mm/rmap.c |    9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff -urpN linux-2.6/mm/rmap.c linux-2.6-patched/mm/rmap.c
--- linux-2.6/mm/rmap.c	2007-11-16 14:27:35.000000000 +0100
+++ linux-2.6-patched/mm/rmap.c	2007-11-16 14:27:43.000000000 +0100
@@ -471,11 +471,12 @@ int page_mkclean(struct page *page)
 
 	if (page_mapped(page)) {
 		struct address_space *mapping = page_mapping(page);
-		if (mapping)
+		if (mapping) {
 			ret = page_mkclean_file(mapping, page);
-		if (page_test_dirty(page)) {
-			page_clear_dirty(page);
-			ret = 1;
+			if (page_test_dirty(page)) {
+				page_clear_dirty(page);
+				ret = 1;
+			}
 		}
 	}
 

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.


  parent reply	other threads:[~2007-11-16 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 14:24 [patch 00/10] 2.6.24-rc s390 patch queue Martin Schwidefsky
2007-11-16 14:24 ` [patch 01/10] cio: change device sense procedure to work with pav aliases Martin Schwidefsky
2007-11-16 14:24 ` [patch 02/10] magic sysrq: check for in_atomic before doing an console_unblank Martin Schwidefsky
2007-11-16 14:24 ` [patch 03/10] Fix irq tracing and lockdep_sys_exit calls Martin Schwidefsky
2007-11-16 14:24 ` [patch 04/10] cmm: remove unused binary sysctls Martin Schwidefsky
2007-11-16 14:24 ` [patch 05/10] appldata: " Martin Schwidefsky
2007-11-16 14:24 ` [patch 06/10] Fix kernel preemption Martin Schwidefsky
2007-11-16 14:24 ` Martin Schwidefsky [this message]
2007-11-16 14:24 ` [patch 08/10] Dont overwrite lowcores on smp_send_stop() Martin Schwidefsky
2007-11-16 14:24 ` [patch 09/10] Explicitly code allocpercpu calls in iucv Martin Schwidefsky
2007-11-16 14:24 ` [patch 10/10] Fix memory detection Martin Schwidefsky

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=20071116142527.252876230@de.ibm.com \
    --to=schwidefsky@de.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox