linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
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, 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 V5 0/4] Refactor do_wp_page, no functional change
Date: Mon, 23 Feb 2015 16:20:05 -0800	[thread overview]
Message-ID: <20150223162005.6eebce98b795699456464df4@linux-foundation.org> (raw)
In-Reply-To: <1424612538-25889-1-git-send-email-raindel@mellanox.com>

On Sun, 22 Feb 2015 15:42:14 +0200 Shachar Raindel <raindel@mellanox.com> wrote:

> Currently do_wp_page contains 265 code lines. It also contains 9 goto
> statements, of which 5 are targeting labels which are not cleanup
> related. This makes the function extremely difficult to
> understand. The following patches are an attempt at breaking the
> function to its basic components, and making it easier to understand.
> 
> The patches are straight forward function extractions from
> do_wp_page. As we extract functions, we remove unneeded parameters and
> simplify the code as much as possible. However, the functionality is
> supposed to remain completely unchanged. The patches also attempt to
> document the functionality of each extracted function. In patch 2, we
> split the unlock logic to the contain logic relevant to specific needs
> of each use case, instead of having huge number of conditional
> decisions in a single unlock flow.

gcc-4.4.4:

   text    data     bss     dec     hex filename
  40898     186   13344   54428    d49c mm/memory.o-before
  41422     186   13456   55064    d718 mm/memory.o-after

gcc-4.8.2:

   text    data     bss     dec     hex filename
  35261   12118   13904   61283    ef63 mm/memory.o
  35646   12278   14032   61956    f204 mm/memory.o

The more recent compiler is more interesting but either way, that's a
somewhat disappointing increase in code size for refactoring of a
single function.

I had a brief poke around and couldn't find any obvious improvements
to make.

--
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>

  parent reply	other threads:[~2015-02-24  0:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 13:42 Shachar Raindel
2015-02-22 13:42 ` [PATCH V5 1/4] mm: Refactor do_wp_page, extract the reuse case Shachar Raindel
2015-02-24 13:39   ` Michal Hocko
2015-02-22 13:42 ` [PATCH V5 2/4] mm: Refactor do_wp_page - rewrite the unlock flow Shachar Raindel
2015-02-24 13:45   ` Michal Hocko
2015-02-22 13:42 ` [PATCH V5 3/4] mm: refactor do_wp_page, extract the page copy flow Shachar Raindel
2015-02-24 13:56   ` Michal Hocko
2015-02-22 13:42 ` [PATCH V5 4/4] mm: Refactor do_wp_page handling of shared vma into a function Shachar Raindel
2015-02-24 13:59   ` Michal Hocko
2015-02-24  0:20 ` Andrew Morton [this message]
2015-02-24  8:36   ` [PATCH V5 0/4] Refactor do_wp_page, no functional change Shachar Raindel

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=20150223162005.6eebce98b795699456464df4@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=ak@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox