From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25628] client should cache negative results
Date: Thu, 18 Mar 2021 16:58:55 +0000 [thread overview]
Message-ID: <bug-25628-10460-3gK14NXLq5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25628-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25628
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|amerey at redhat dot com |alizhang at redhat dot com
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
Suggest implementing this via:
- map a 404 result code to an empty 000-permission file in the debuginfod
client cache
- when querying for a buildid, if the cache includes such a 000-permission
file, check its fstat
- if the fstat mtime is older than the configuration parameter from the file
.cache/cache_miss_s, then unlink the 000 file and proceed with a new query
- if the fstat mtime is newer, then the 000 file is fresh, so return a
404/ENOENT equivalent to the debuginfod client application
- a good default for cache_miss_s could be 600 (10 minutes)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-18 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:09 [Bug debuginfod/25628] New: " amerey at redhat dot com
2020-03-03 16:24 ` [Bug debuginfod/25628] " fche at redhat dot com
2020-03-03 20:30 ` amerey at redhat dot com
2020-03-03 20:31 ` amerey at redhat dot com
2021-03-18 16:58 ` fche at redhat dot com [this message]
2021-05-06 21:21 ` fche at redhat dot com
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=bug-25628-10460-3gK14NXLq5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).