From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Shachar Raindel <raindel@mellanox.com>
Cc: linux-mm@kvack.org, kirill.shutemov@linux.intel.com,
mgorman@suse.de, riel@redhat.com, ak@linux.intel.com,
matthew.r.wilcox@intel.com, dave.hansen@linux.intel.com,
n-horiguchi@ah.jp.nec.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, haggaie@mellanox.com,
aarcange@redhat.com, pfeiner@google.com, hannes@cmpxchg.org,
sagig@mellanox.com, walken@google.com
Subject: Re: [PATCH 4/5] mm: Refactor do_wp_page handling of shared vma into a function
Date: Mon, 1 Dec 2014 15:03:16 +0200 [thread overview]
Message-ID: <20141201130316.GE13856@node.dhcp.inet.fi> (raw)
In-Reply-To: <1417435485-24629-5-git-send-email-raindel@mellanox.com>
On Mon, Dec 01, 2014 at 02:04:44PM +0200, Shachar Raindel wrote:
> The do_wp_page function is extremely long. Extract the logic for
> handling a page belonging to a shared vma into a function of its own.
>
> This helps the readability of the code, without doing any functional
> change in it.
>
> Signed-off-by: Shachar Raindel <raindel@mellanox.com>
> ---
> mm/memory.c | 87 ++++++++++++++++++++++++++++++++++---------------------------
> 1 file changed, 49 insertions(+), 38 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 436012d..8023cf3 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -2248,6 +2248,53 @@ oom:
> return VM_FAULT_OOM;
> }
>
> +static int wp_page_shared_vma(struct mm_struct *mm, struct vm_area_struct *vma,
wp_page_shared() is enough. no need in _vma.
> + unsigned long address, pte_t *page_table,
> + pmd_t *pmd, spinlock_t *ptl, pte_t orig_pte,
> + struct page *old_page)
> + __releases(ptl)
> +{
> + int page_mkwrite = 0;
> +
> + /*
> + * Only catch write-faults on shared writable pages,
> + * read-only shared pages can get COWed by
> + * get_user_pages(.write=1, .force=1).
> + */
> + if (vma->vm_ops && vma->vm_ops->page_mkwrite) {
Inversion of the check would help indentation level of the code below.
> + int tmp;
> +
> + page_cache_get(old_page);
> + pte_unmap_unlock(page_table, ptl);
> + tmp = do_page_mkwrite(vma, old_page, address);
> + if (unlikely(!tmp || (tmp &
> + (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))) {
> + page_cache_release(old_page);
> + return tmp;
> + }
> + /*
> + * Since we dropped the lock we need to revalidate
> + * the PTE as someone else may have changed it. If
> + * they did, we just return, as we can count on the
> + * MMU to tell us if they didn't also make it writable.
> + */
> + page_table = pte_offset_map_lock(mm, pmd, address,
> + &ptl);
> + if (!pte_same(*page_table, orig_pte)) {
> + unlock_page(old_page);
> + return wp_page_unlock(mm, vma, page_table, ptl,
> + 0, 0,
> + old_page, 0);
> + }
> +
> + page_mkwrite = 1;
> + }
> + get_page(old_page);
> +
> + return wp_page_reuse(mm, vma, address, page_table, ptl, orig_pte,
> + old_page, 1, page_mkwrite);
> +}
> +
> /*
> * This routine handles present pages, when users try to write
> * to a shared page. It is done by copying the page to a new address
> @@ -2324,44 +2371,8 @@ static int do_wp_page(struct mm_struct *mm, struct vm_area_struct *vma,
> unlock_page(old_page);
> } else if (unlikely((vma->vm_flags & (VM_WRITE|VM_SHARED)) ==
> (VM_WRITE|VM_SHARED))) {
> - int page_mkwrite = 0;
> -
> - /*
> - * Only catch write-faults on shared writable pages,
> - * read-only shared pages can get COWed by
> - * get_user_pages(.write=1, .force=1).
> - */
> - if (vma->vm_ops && vma->vm_ops->page_mkwrite) {
> - int tmp;
> - page_cache_get(old_page);
> - pte_unmap_unlock(page_table, ptl);
> - tmp = do_page_mkwrite(vma, old_page, address);
> - if (unlikely(!tmp || (tmp &
> - (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))) {
> - page_cache_release(old_page);
> - return tmp;
> - }
> - /*
> - * Since we dropped the lock we need to revalidate
> - * the PTE as someone else may have changed it. If
> - * they did, we just return, as we can count on the
> - * MMU to tell us if they didn't also make it writable.
> - */
> - page_table = pte_offset_map_lock(mm, pmd, address,
> - &ptl);
> - if (!pte_same(*page_table, orig_pte)) {
> - unlock_page(old_page);
> - return wp_page_unlock(mm, vma, page_table, ptl,
> - 0, 0,
> - old_page, 0);
> - }
> -
> - page_mkwrite = 1;
> - }
> - get_page(old_page);
> -
> - return wp_page_reuse(mm, vma, address, page_table, ptl,
> - orig_pte, old_page, 1, page_mkwrite);
> + return wp_page_shared_vma(mm, vma, address, page_table, pmd,
> + ptl, orig_pte, old_page);
> }
>
> /*
> --
> 1.7.11.2
>
> --
> 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>
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2014-12-01 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 12:04 [PATCH 0/5] Refactor do_wp_page, no functional change Shachar Raindel
2014-12-01 12:04 ` [PATCH 1/5] mm: Refactor do_wp_page, extract the reuse case Shachar Raindel
2014-12-01 12:30 ` Kirill A. Shutemov
2014-12-01 12:34 ` Shachar Raindel
2014-12-01 12:50 ` Kirill A. Shutemov
2014-12-01 12:04 ` [PATCH 2/5] mm: Refactor do_wp_page - extract the unlock flow Shachar Raindel
2014-12-01 12:43 ` Kirill A. Shutemov
2014-12-01 12:04 ` [PATCH 3/5] mm: refactor do_wp_page, extract the page copy flow Shachar Raindel
2014-12-01 12:57 ` Kirill A. Shutemov
2014-12-01 12:04 ` [PATCH 4/5] mm: Refactor do_wp_page handling of shared vma into a function Shachar Raindel
2014-12-01 13:03 ` Kirill A. Shutemov [this message]
2014-12-01 12:04 ` [PATCH 5/5] mm: Move the MMU-notifier code from wp_page_unlock to wp_page_copy Shachar Raindel
2014-12-01 16:47 ` [PATCH 0/5] Refactor do_wp_page, no functional change Linus Torvalds
2014-12-01 16:53 ` Andi Kleen
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=20141201130316.GE13856@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=haggaie@mellanox.com \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mgorman@suse.de \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pfeiner@google.com \
--cc=raindel@mellanox.com \
--cc=riel@redhat.com \
--cc=sagig@mellanox.com \
--cc=torvalds@linux-foundation.org \
--cc=walken@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 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.