From: Hillf Danton <dhillf@gmail.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.cz>
Subject: [PATCH] ksm: use FAULT_FLAG_ALLOW_RETRY in breaking COW
Date: Sat, 19 Nov 2011 19:50:19 +0800 [thread overview]
Message-ID: <CAJd=RBDP_z68Ewvw_O_dMxOnE0=weXqt+1FQy85_n76HAEdFHg@mail.gmail.com> (raw)
The flag, FAULT_FLAG_ALLOW_RETRY, was introduced by the patch,
mm: retry page fault when blocking on disk transfer
commit: d065bd810b6deb67d4897a14bfe21f8eb526ba99
for reducing mmap_sem hold times that are caused by waiting for disk
transfers when accessing file mapped VMAs.
To break COW, handle_mm_fault() is repeated with mmap_sem held, where
the introduced flag could be used again.
The straight way is to add changes in break_ksm(), but the function could be
under write-mode mmap_sem, so it has to be dupilcated.
Signed-off-by: Hillf Danton <dhillf@gmail.com>
---
--- a/mm/ksm.c Sat Nov 19 16:08:10 2011
+++ b/mm/ksm.c Sat Nov 19 19:33:49 2011
@@ -394,7 +394,31 @@ static void break_cow(struct rmap_item *
goto out;
if (!(vma->vm_flags & VM_MERGEABLE) || !vma->anon_vma)
goto out;
- break_ksm(vma, addr);
+ for (;;) {
+ struct page *page;
+ int ret;
+
+ page = follow_page(vma, addr, FOLL_GET);
+ if (IS_ERR_OR_NULL(page))
+ break;
+
+ if (PageKsm(page))
+ ret = handle_mm_fault(mm, vma, addr,
+ FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_WRITE);
+ else
+ ret = VM_FAULT_WRITE;
+
+ put_page(page);
+
+ if (!(ret & (VM_FAULT_WRITE|VM_FAULT_SIGBUS|VM_FAULT_OOM))) {
+ if (ret & VM_FAULT_RETRY)
+ down_read(&mm->mmap_sem);
+ } else {
+ if (ret & VM_FAULT_RETRY)
+ return;
+ break;
+ }
+ }
out:
up_read(&mm->mmap_sem);
}
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-11-19 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 11:50 Hillf Danton [this message]
2011-11-21 4:16 ` Hugh Dickins
2011-11-21 13:47 ` Hillf Danton
2011-11-21 22:23 ` Hugh Dickins
2011-11-22 13:04 ` Hillf Danton
2011-11-21 23:10 ` Michel Lespinasse
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='CAJd=RBDP_z68Ewvw_O_dMxOnE0=weXqt+1FQy85_n76HAEdFHg@mail.gmail.com' \
--to=dhillf@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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