From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Noah Sanci <nsanci@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: PR: 25978
Date: Thu, 8 Jul 2021 09:12:20 -0400 [thread overview]
Message-ID: <20210708131220.GB31689@redhat.com> (raw)
In-Reply-To: <6360cc559a7ab536688ce70e79fc6334709eddee.camel@klomp.org>
Hi -
> If they are portions of the full fdcache shouldn't there be a check in
> the code that the specified fdcache_prefetch_fds and
> fdcache_prefetch_mbs aren't larger than fdcache_fds and fdcache_mbs? Or
> maybe they should be given as percentages?
We've iterated on a couple of ways of representing & controlling this.
The code makes the lru and prefetch caches separate, in that they have
separate limits and separate metrics. So there is no requirement for
the prefetch one to be smaller than the other. (We will probably want
to tweak the defaults to be a little larger at some point.)
- FChE
next prev parent reply other threads:[~2021-07-08 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 18:24 Noah Sanci
2021-07-08 13:07 ` Mark Wielaard
2021-07-08 13:12 ` Frank Ch. Eigler [this message]
2021-07-08 15:04 ` Mark Wielaard
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=20210708131220.GB31689@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
--cc=nsanci@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).