public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ihor.solodrai@pm.me, eddyz87@gmail.com, dwarves@vger.kernel.org
Subject: Re: [PATCH dwarves] btf_encoder: use ELF_C_READ_MMAP
Date: Fri, 18 Oct 2024 09:59:22 -0300	[thread overview]
Message-ID: <ZxJbqhus4Io4_1bg@x1> (raw)
In-Reply-To: <20241014103142.2280044-1-alan.maguire@oracle.com>

On Mon, Oct 14, 2024 at 11:31:42AM +0100, Alan Maguire wrote:
> This reduces peak memory utilization during BTF vmlinux encoding,
> replacing ELF section-sized malloc()s with mmap()s.
> 
> For -j1 peak memory resident set size drops from
> 
>         Maximum resident set size (kbytes): 1069220
> 
> ...to:
> 
>         Maximum resident set size (kbytes): 701888
> 
> ...with this patch.
> 
> For -j8, peak memory resident set size drops from
> 
>         Maximum resident set size (kbytes): 1121172
> 
> ...to:
> 
>         Maximum resident set size (kbytes): 963516

Thanks, applied to perf-tools-next,

- Arnaldo
 
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
>  btf_encoder.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/btf_encoder.c b/btf_encoder.c
> index 5954238..9599faf 100644
> --- a/btf_encoder.c
> +++ b/btf_encoder.c
> @@ -1879,7 +1879,7 @@ static int btf_encoder__tag_kfuncs(struct btf_encoder *encoder)
>  		goto out;
>  	}
>  
> -	elf = elf_begin(fd, ELF_C_READ, NULL);
> +	elf = elf_begin(fd, ELF_C_READ_MMAP, NULL);
>  	if (elf == NULL) {
>  		elf_error("Cannot update ELF file");
>  		goto out;
> -- 
> 2.43.5

      parent reply	other threads:[~2024-10-18 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 10:31 [PATCH dwarves] btf_encoder: use ELF_C_READ_MMAP Alan Maguire
2024-10-14 16:21 ` Ihor Solodrai
2024-10-18 12:59 ` Arnaldo Carvalho de Melo [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=ZxJbqhus4Io4_1bg@x1 \
    --to=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@pm.me \
    /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