Linux debuggers
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: elfutils-devel@sourceware.org, linux-debuggers@vger.kernel.org
Subject: Re: [PATCH v3 0/7] debuginfod: speed up extraction from kernel debuginfo packages by 200x
Date: Fri, 19 Jul 2024 13:34:48 -0400	[thread overview]
Message-ID: <20240719173448.GB27443@redhat.com> (raw)
In-Reply-To: <cover.1721377314.git.osandov@fb.com>

Hi -

> This is v3 of my patch series optimizing debuginfod for kernel
> debuginfo.  v1 is here [7], v2 is here [8].  This version fixes a couple
> of minor bugs and adds test cases. [...]

Thanks, LGTM, running through try-buildbots to make sure.

- FChE


  parent reply	other threads:[~2024-07-19 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19  8:31 [PATCH v3 0/7] debuginfod: speed up extraction from kernel debuginfo packages by 200x Omar Sandoval
2024-07-19  8:31 ` [PATCH v3 1/7] debuginfod: fix skipping <built-in> source file Omar Sandoval
2024-07-19  8:31 ` [PATCH v3 2/7] tests/run-debuginfod-fd-prefetch-caches.sh: disable fdcache limit check Omar Sandoval
2024-07-19  8:31 ` [PATCH v3 3/7] debuginfod: factor out common code for responding from an archive Omar Sandoval
2024-07-19  8:32 ` [PATCH v3 4/7] debugifod: add new table and views for seekable archives Omar Sandoval
2024-07-19  8:32 ` [PATCH v3 5/7] debuginfod: optimize extraction from seekable xz archives Omar Sandoval
2024-07-19  8:32 ` [PATCH v3 6/7] debuginfod: populate _r_seekable on scan Omar Sandoval
2024-07-19  8:32 ` [PATCH v3 7/7] debuginfod: populate _r_seekable on request Omar Sandoval
2024-07-19 17:34 ` Frank Ch. Eigler [this message]
2024-07-19 18:04   ` [PATCH v3 0/7] debuginfod: speed up extraction from kernel debuginfo packages by 200x Omar Sandoval

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=20240719173448.GB27443@redhat.com \
    --to=fche@redhat.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=linux-debuggers@vger.kernel.org \
    --cc=osandov@osandov.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