linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/5] report allocation stats
Date: Wed, 12 Apr 2017 10:36:58 +0200	[thread overview]
Message-ID: <20170412083703.11552-1-luc.vanoostenryck@gmail.com> (raw)

The goal of this series is to add some support to easily
report allocations statistics and thus be able to do
some experiments about allocation.

For example, playing a bit with this showed that most lists
are quite short (can be as short as and avarage of 2.5 elements
on some code) and that decreasing LIST_NODE_NR from 29 to 13
allow to win 5% when using make C=2 on the kernel (when all
source files have already been compile by GCC), which is already
quite interesting..


This series is available at:
	git://github.com/lucvoo/sparse.git alloc-stats
based on commits (a merge):
	263f8ce449097da4caacfac4e00144f626c6e6a7 (pre-llvm-fixes-v6)
	fc981fe285c37ee297e93ef1cc8725caac75f9b3 (fix-bitfield-init-v2
up to commit:
	bdd16ed276569a16b2362adb266048b91e617f32

Luc Van Oostenryck (5):
  add get_<allocator>_stats()
  add show_allocation_stats()
  add helper handle_simple_switch()
  teach sparse how to handle '-fmem-report'
  use -fmem-report to report allocation stats


 Makefile         |  1 +
 allocate.c       |  8 ++++++++
 allocate.h       | 13 ++++++++++++
 lib.c            | 26 ++++++++++++++++++++----
 lib.h            |  2 ++
 sparse-llvm.c    |  1 +
 sparse.1         |  4 ++++
 sparse.c         |  2 ++
 stats.c          | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 test-linearize.c |  2 ++
 test-unssa.c     |  1 +
 11 files changed, 118 insertions(+), 4 deletions(-)
 create mode 100644 stats.c

-- 
2.12.0


             reply	other threads:[~2017-04-12  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  8:36 Luc Van Oostenryck [this message]
2017-04-12  8:36 ` [PATCH 1/5] add get_<allocator>_stats() Luc Van Oostenryck
2017-04-12  8:37 ` [PATCH 2/5] add show_allocation_stats() Luc Van Oostenryck
2017-04-12  8:37 ` [PATCH 3/5] add helper handle_simple_switch() Luc Van Oostenryck
2017-06-01  6:15   ` Christopher Li
2017-06-01 14:30     ` Luc Van Oostenryck
2017-04-12  8:37 ` [PATCH 4/5] teach sparse how to handle '-fmem-report' Luc Van Oostenryck
2017-04-12  8:37 ` [PATCH 5/5] use -fmem-report to report allocation stats Luc Van Oostenryck

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=20170412083703.11552-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).