From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: patch to commit soon: PR25375 debuginfod prefetching
Date: Tue, 25 Feb 2020 14:49:00 -0000 [thread overview]
Message-ID: <20200225144911.GB29007@redhat.com> (raw)
In-Reply-To: <c462f67e934e7f0af52459496d017805a672014b.camel@klomp.org>
Hi -
> > + fdcache_prefetch = 64; // guesstimate storage is this much less costly than re-decompression
> > + fdcache_fds = (concurrency + fdcache_prefetch) * 2;
>
> Here fdcache_prefetch is set and used before argp_parse () is called,
> which would set it to the user supplied value (if any). Is that
> intentional?
Yeah, the idea is to provide some reasonable defaults, and then allow
the command line options to override them. In this case, the user
might want to override both. It'll be specific to the site anyway,
depending on distribution of rpm sizes vs. available storage.
- FChE
prev parent reply other threads:[~2020-02-25 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 22:29 Frank Ch. Eigler
2020-02-25 11:32 ` Mark Wielaard
2020-02-25 14:49 ` Frank Ch. Eigler [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=20200225144911.GB29007@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).