From: Pedro Alves <palves@redhat.com>
To: lgustavo@codesourcery.com
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Tom Tromey <tromey@redhat.com>,
"Maciej W. Rozycki" <macro@codesourcery.com>
Subject: Re: Unreliable BFD caching heuristic
Date: Mon, 25 Nov 2013 18:21:00 -0000 [thread overview]
Message-ID: <52939510.7000308@redhat.com> (raw)
In-Reply-To: <52938CB2.8080700@codesourcery.com>
On 11/25/2013 05:45 PM, Luis Machado wrote:
> We can't rely on the timestamp due to some filesystems having 1 second
> or 2 seconds resolution. That doesn't seem enough.
We can't rely on timestamps to be sure the files are the same, but
we can assume that if the files have different timestamps, they're
not the same. IOW, if we have some other fallback file comparison
method that is more expensive, we only need to apply it if the
timestamps match; if they don't match, we can assume the file
is not the same. Sure, if the same file is accessed through
different filesystems, we can end up thinking we had two handles
for different files, but then all that's lost is we don't apply the
bfd sharing optimization in that rare scenario.
--
Pedro Alves
next prev parent reply other threads:[~2013-11-25 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 17:39 Luis Machado
2013-11-21 17:58 ` Pedro Alves
2013-11-21 21:58 ` Tom Tromey
2013-11-23 12:14 ` Phi Debian
2013-11-25 17:45 ` Luis Machado
2013-11-25 18:07 ` Pedro Alves
2013-11-25 18:08 ` Maciej W. Rozycki
2013-11-25 18:21 ` Pedro Alves [this message]
2013-12-02 15:42 ` Tom Tromey
2013-12-03 15:28 ` Luis Machado
[not found] ` <CAC=yr6DRDsRLStnDNZW_2=0vOQY-oJHd55_nLUeb8Qetxo=yXw@mail.gmail.com>
2013-12-04 0:01 ` Luis Machado
2013-12-04 3:47 ` Eli Zaretskii
2013-12-04 15:54 ` Tom Tromey
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=52939510.7000308@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=macro@codesourcery.com \
--cc=tromey@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