From: Don Zickus <dzickus@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@ghostprotocols.net, LKML <linux-kernel@vger.kernel.org>,
jmario@redhat.com, fowles@inreach.com,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 2/4] perf, kmem: Utilize the new generic cpunode_map
Date: Mon, 31 Mar 2014 22:42:30 -0400 [thread overview]
Message-ID: <20140401024230.GR25953@redhat.com> (raw)
In-Reply-To: <20140329171047.GC2022@krava.redhat.com>
On Sat, Mar 29, 2014 at 06:10:47PM +0100, Jiri Olsa wrote:
> On Mon, Mar 24, 2014 at 03:32:55PM -0400, Don Zickus wrote:
> > Use the previous patch implementation of cpunode_map for builtin-kmem.c
> > Should not be any functional difference.
> >
> > Cc: Li Zefan <lizf@cn.fujitsu.com>
> > Signed-off-by: Don Zickus <dzickus@redhat.com>
> > ---
> > tools/perf/builtin-kmem.c | 78 ++---------------------------------------------
> > 1 file changed, 3 insertions(+), 75 deletions(-)
> >
> > diff --git a/tools/perf/builtin-kmem.c b/tools/perf/builtin-kmem.c
> > index 929462a..a61783a 100644
> > --- a/tools/perf/builtin-kmem.c
> > +++ b/tools/perf/builtin-kmem.c
> > @@ -14,6 +14,7 @@
> > #include "util/parse-options.h"
> > #include "util/trace-event.h"
> > #include "util/data.h"
> > +#include "util/cpumap.h"
> >
> > #include "util/debug.h"
> >
> > @@ -31,9 +32,6 @@ static int caller_lines = -1;
> >
> > static bool raw_ip;
> >
> > -static int *cpunode_map;
> > -static int max_cpu_num;
> > -
> > struct alloc_stat {
> > u64 call_site;
> > u64 ptr;
> > @@ -55,76 +53,6 @@ static struct rb_root root_caller_sorted;
> > static unsigned long total_requested, total_allocated;
> > static unsigned long nr_allocs, nr_cross_allocs;
> >
> > -#define PATH_SYS_NODE "/sys/devices/system/node"
> > -
> > -static int init_cpunode_map(void)
> > -{
> > - FILE *fp;
> > - int i, err = -1;
> > -
> > - fp = fopen("/sys/devices/system/cpu/kernel_max", "r");
>
> so the factored code from previous patches now reads
> the max_cpu_num value from:
> /sys/devices/system/cpu/possible
>
> is this intentional?
Yeah, I was trying to save bits. No need to allocate for 5100 cpus when
only 128 are used.
>
> I think we want to have separate patches for code changes
> and for changing the file with some comment.
So you want me to split the previous patch into two. One for code
movement, the other for the path change?
Cheers,
Don
>
> jirka
next prev parent reply other threads:[~2014-04-01 2:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 19:32 [PATCH 0/4] perf: Make some functions generic Don Zickus
2014-03-24 19:32 ` [PATCH 1/4] perf: Allow ability to map cpus to nodes easily Don Zickus
2014-03-29 17:10 ` Jiri Olsa
2014-04-01 2:39 ` Don Zickus
2014-04-06 12:19 ` Jiri Olsa
2014-04-03 5:48 ` Namhyung Kim
2014-04-06 12:15 ` Jiri Olsa
2014-04-07 5:28 ` Namhyung Kim
2014-04-07 18:20 ` Don Zickus
2014-03-24 19:32 ` [PATCH 2/4] perf, kmem: Utilize the new generic cpunode_map Don Zickus
2014-03-29 17:10 ` Jiri Olsa
2014-04-01 2:42 ` Don Zickus [this message]
2014-04-06 12:21 ` Jiri Olsa
2014-04-07 18:18 ` Don Zickus
2014-03-24 19:32 ` [PATCH 3/4] perf, callchain: Add generic report parse callchain callback function Don Zickus
2014-03-29 17:11 ` Jiri Olsa
2014-04-03 5:57 ` Namhyung Kim
2014-04-04 19:31 ` Don Zickus
2014-04-06 12:11 ` Jiri Olsa
2014-04-07 5:15 ` Namhyung Kim
2014-04-07 7:01 ` Jiri Olsa
2014-03-24 19:32 ` [PATCH 4/4] perf, report: Use new generic report parse callchain callback Don Zickus
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=20140401024230.GR25953@redhat.com \
--to=dzickus@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=fowles@inreach.com \
--cc=jmario@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).