From: Tim Chen <tim.c.chen@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Vincent Donnefort <vdonnefort@google.com>,
Sven Schnelle <svens@linux.ibm.com>,
Mete Durlu <meted@linux.ibm.com>
Subject: Re: [PATCH] tracing: Have saved_cmdlines arrays all in one allocation
Date: Mon, 12 Feb 2024 15:39:03 -0800 [thread overview]
Message-ID: <ef94259e139e4579ee27db99975dc4cf397e2a06.camel@linux.intel.com> (raw)
In-Reply-To: <20240212180941.379c419b@gandalf.local.home>
On Mon, 2024-02-12 at 18:09 -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> The saved_cmdlines have three arrays for mapping PIDs to COMMs:
>
> - map_pid_to_cmdline[]
> - map_cmdline_to_pid[]
> - saved_cmdlines
>
> The map_pid_to_cmdline[] is PID_MAX_DEFAULT in size and holds the index
> into the other arrays. The map_cmdline_to_pid[] is a mapping back to the
> full pid as it can be larger than PID_MAX_DEFAULT. And the
> saved_cmdlines[] just holds the COMMs associated to the pids.
>
> Currently the map_pid_to_cmdline[] and saved_cmdlines[] are allocated
> together (in reality the saved_cmdlines is just in the memory of the
> rounding of the allocation of the structure as it is always allocated in
> powers of two). The map_cmdline_to_pid[] array is allocated separately.
>
> Since the rounding to a power of two is rather large (it allows for 8000
> elements in saved_cmdlines), also include the map_cmdline_to_pid[] array.
> (This drops it to 6000 by default, which is still plenty for most use
> cases). This saves even more memory as the map_cmdline_to_pid[] array
> doesn't need to be allocated.
This patch does make better use of the extra space and make the
previous change better.
Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
>
> Link: https://lore.kernel.org/linux-trace-kernel/20240212174011.068211d9@gandalf.local.home/
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_sched_switch.c | 13 ++++---------
> 1 file changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/trace/trace_sched_switch.c b/kernel/trace/trace_sched_switch.c
> index e4fbcc3bede5..210c74dcd016 100644
> --- a/kernel/trace/trace_sched_switch.c
> +++ b/kernel/trace/trace_sched_switch.c
> @@ -201,7 +201,7 @@ static struct saved_cmdlines_buffer *allocate_cmdlines_buffer(unsigned int val)
> int order;
>
> /* Figure out how much is needed to hold the given number of cmdlines */
> - orig_size = sizeof(*s) + val * TASK_COMM_LEN;
> + orig_size = sizeof(*s) + val * (TASK_COMM_LEN + sizeof(int));
Strictly speaking, *map_cmdline_to_pid is unsigned int so it is more consistent
to use sizeof(unsigned) in line above. But I'm nitpicking and I'm fine to
leave it as is.
> order = get_order(orig_size);
> size = 1 << (order + PAGE_SHIFT);
> page = alloc_pages(GFP_KERNEL, order);
> @@ -212,16 +212,11 @@ static struct saved_cmdlines_buffer *allocate_cmdlines_buffer(unsigned int val)
> memset(s, 0, sizeof(*s));
>
> /* Round up to actual allocation */
> - val = (size - sizeof(*s)) / TASK_COMM_LEN;
> + val = (size - sizeof(*s)) / (TASK_COMM_LEN + sizeof(int));
> s->cmdline_num = val;
>
> - s->map_cmdline_to_pid = kmalloc_array(val,
> - sizeof(*s->map_cmdline_to_pid),
> - GFP_KERNEL);
> - if (!s->map_cmdline_to_pid) {
> - free_saved_cmdlines_buffer(s);
> - return NULL;
> - }
> + /* Place map_cmdline_to_pid array right after saved_cmdlines */
> + s->map_cmdline_to_pid = (unsigned *)&s->saved_cmdlines[val * TASK_COMM_LEN];
>
> s->cmdline_idx = 0;
> memset(&s->map_pid_to_cmdline, NO_CMDLINE_MAP,
next prev parent reply other threads:[~2024-02-12 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 23:09 [PATCH] tracing: Have saved_cmdlines arrays all in one allocation Steven Rostedt
2024-02-12 23:36 ` Masami Hiramatsu
2024-02-12 23:39 ` Tim Chen [this message]
2024-02-13 0:13 ` Steven Rostedt
2024-02-13 16:35 ` Tim Chen
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=ef94259e139e4579ee27db99975dc4cf397e2a06.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=meted@linux.ibm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=vdonnefort@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