From: Doug Evans <xdje42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] symbol lookup cache
Date: Sat, 20 Dec 2014 19:14:00 -0000 [thread overview]
Message-ID: <CAP9bCMTemYD6-X55OMacphFY6PcAan8Vr9E_Rh43KN=x4_NB7Q@mail.gmail.com> (raw)
In-Reply-To: <83d27esisa.fsf@gnu.org>
On Sat, Dec 20, 2014 at 2:43 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Doug Evans <xdje42@gmail.com>
>> Date: Fri, 19 Dec 2014 23:56:23 -0800
>>
>> Here is an updated patch for the symbol cache,
>> with docs and ChangeLog entry.
>
> Btw, I wonder if this should be a user option, not a "maint" option.
> The heuristics used to determine the cache size tend to be wrong in
> some rare corner cases, so letting the user override this should be a
> good thing, I think.
The thought is the fewer knobs the user needs the better,
and that's where potentially dynamically adjusting the size comes in.
It's easier to remove/change maint options, so for now I put the size there
until there's data to guide a better choice.
But, ultimately, making it a user-settable option is definitely a possibility.
next prev parent reply other threads:[~2014-12-20 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 8:23 [RFC] " Doug Evans
2014-12-03 0:50 ` Doug Evans
2014-12-20 7:57 ` [PATCH] " Doug Evans
2014-12-20 8:29 ` Doug Evans
2014-12-20 10:43 ` Eli Zaretskii
2014-12-20 19:14 ` Doug Evans [this message]
2014-12-20 19:55 ` Eli Zaretskii
2014-12-20 21:04 ` Doug Evans
2014-12-21 3:34 ` Eli Zaretskii
2014-12-21 18:51 ` Doug Evans
2014-12-21 21:01 ` Joel Brobecker
2014-12-22 2:04 ` Doug Evans
2014-12-22 12:48 ` Joel Brobecker
2015-01-11 19:11 ` Doug Evans
2014-12-03 2:46 ` [RFC] " Joel Brobecker
2014-12-04 16:38 ` Pedro Alves
2014-12-04 19:17 ` Doug Evans
2014-12-04 19:16 ` Jan Kratochvil
2014-12-04 19:24 ` Doug Evans
2014-12-04 19:28 ` Jan Kratochvil
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='CAP9bCMTemYD6-X55OMacphFY6PcAan8Vr9E_Rh43KN=x4_NB7Q@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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