From: David Howells <dhowells@redhat.com>
To: Milosz Tanski <milosz@adfin.com>
Cc: NeilBrown <neilb@suse.de>,
ceph-devel <ceph-devel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-cachefs@redhat.com" <linux-cachefs@redhat.com>
Subject: Re: fscache recursive hang -- similar to loopback NFS issues
Date: Tue, 05 Aug 2014 15:32:46 +0100 [thread overview]
Message-ID: <20765.1407249166@warthog.procyon.org.uk> (raw)
In-Reply-To: <CANP1eJGoT2RmKB6asjbFgP=emLuxQqgqE4Xf9Gx7fYzPfS1img@mail.gmail.com>
Milosz Tanski <milosz@adfin.com> wrote:
> FSCache already tracks statistics about how long writes and reads take
> (at least if you enable that option). With those stats in hand we
> should be able generate a default timeout value that works well and
> avoid a tunable.
If stat generation is going to be on all the time, it should probably use
something other than atomic ops. NFS uses a set of ints on each CPU which are
added together when needed.
David
prev parent reply other threads:[~2014-08-05 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 20:20 fscache recursive hang -- similar to loopback NFS issues Milosz Tanski
2014-07-19 20:31 ` Milosz Tanski
2014-07-21 6:40 ` NeilBrown
2014-07-21 11:42 ` Milosz Tanski
2014-07-29 16:12 ` David Howells
2014-07-29 21:17 ` NeilBrown
2014-07-30 1:48 ` Milosz Tanski
2014-07-30 2:19 ` NeilBrown
2014-07-30 16:06 ` Milosz Tanski
2014-08-05 4:12 ` Milosz Tanski
2014-08-05 4:49 ` NeilBrown
2014-08-05 14:32 ` David Howells [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=20765.1407249166@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=neilb@suse.de \
/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