All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
	ben@decadent.org.uk, hannes@cmpxchg.org, vdavydov@virtuozzo.com,
	linux-mm@kvack.org
Subject: Re: + memcg-fix-thresholds-for-32b-architectures-fix-fix.patch added to -mm tree
Date: Sat, 7 Nov 2015 23:23:09 +0900	[thread overview]
Message-ID: <20151107142309.GA537@swordfish> (raw)
In-Reply-To: <20151105183132.0a5f874c7f5f69b3c2e53dd1@linux-foundation.org>

Hi,

On (11/05/15 18:31), Andrew Morton wrote:
> > On Tue 03-11-15 15:32:11, Andrew Morton wrote:
> > > From: Andrew Morton <akpm@linux-foundation.org>
> > > Subject: memcg-fix-thresholds-for-32b-architectures-fix-fix
> > > 
> > > don't attempt to inline mem_cgroup_usage()
> > > 
> > > The compiler ignores the inline anwyay.  And __always_inlining it adds 600
> > > bytes of goop to the .o file.
> > 
> > I am not sure you whether you want to fold this into the original patch
> > but I would prefer this to be a separate one.
> 
> I'm going to drop this - it was already marked inline and gcc just
> ignores the inline anyway so shrug.
> 

Just out of curiosity, seems that my gcc (5.2) is happy to inline
it (as of linux-next-20151106):

$ grep 'mem_cgroup_usage ' __ipa_build_log
  Inlining page_counter_read into mem_cgroup_usage (always_inline).
  Inlining page_counter_read into mem_cgroup_usage (always_inline).
  Inlining mem_cgroup_is_root into mem_cgroup_usage (always_inline).
  Inlining mem_cgroup_usage into mem_cgroup_read_u64 (always_inline).
  Inlining mem_cgroup_usage into mem_cgroup_read_u64 (always_inline).
  Inlining mem_cgroup_usage into __mem_cgroup_threshold (always_inline).
  Inlining mem_cgroup_usage into __mem_cgroup_usage_unregister_event (always_inline).
  Inlining mem_cgroup_usage into __mem_cgroup_usage_unregister_event (always_inline).
  Inlining mem_cgroup_usage into __mem_cgroup_usage_register_event (always_inline).
  Inlining mem_cgroup_usage into __mem_cgroup_usage_register_event (always_inline).


and the resulting vmlinux.o files

$ ./scripts/bloat-o-meter vmlinux.o.old vmlinux.o
add/remove: 1/0 grow/shrink: 0/4 up/down: 113/-351 (-238)
function                                     old     new   delta
mem_cgroup_usage                               -     113    +113
__mem_cgroup_usage_unregister_event          409     331     -78
__mem_cgroup_threshold                       529     447     -82
__mem_cgroup_usage_register_event            498     403     -95
mem_cgroup_read_u64                          256     160     -96

	-ss

--
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-11-07 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 23:32 + memcg-fix-thresholds-for-32b-architectures-fix-fix.patch added to -mm tree akpm
2015-11-04  9:18 ` Michal Hocko
2015-11-06  2:31   ` Andrew Morton
2015-11-06  9:52     ` Michal Hocko
2015-11-07 14:23     ` Sergey Senozhatsky [this message]

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=20151107142309.GA537@swordfish \
    --to=sergey.senozhatsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=vdavydov@virtuozzo.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.