From: David Howells <dhowells@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: dhowells@redhat.com, linux-btrfs@vger.kernel.org,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH/RFC] fscache/cachefiles versus btrfs
Date: Thu, 09 Apr 2015 10:23:08 +0100 [thread overview]
Message-ID: <29536.1428571388@warthog.procyon.org.uk> (raw)
In-Reply-To: <20150409174916.5a2efef5@notabene.brown>
NeilBrown <neilb@suse.de> wrote:
> Is there a better way? Could a better way be created? Maybe
> SEEK_DATA_RELIABLE ??
fiemap() maybe?
> Also, if you do try to use fscache on btrfs with 3.19, then nothing gets
> cached (as expected) and with a heavy load you can lose a race and get an
> asserting fail in fscache_enqueue_operation
Do you have the patches here applied?
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-fixes
David
next prev parent reply other threads:[~2015-04-09 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 7:49 [PATCH/RFC] fscache/cachefiles versus btrfs NeilBrown
2015-04-09 9:23 ` David Howells [this message]
2015-04-09 23:52 ` Dave Chinner
2015-04-10 0:42 ` NeilBrown
2015-04-10 1:08 ` Dave Chinner
2015-04-10 13:28 ` David Howells
2015-04-13 17:30 ` Christoph Hellwig
2015-04-10 1:24 ` NeilBrown
2015-04-20 4:49 ` NeilBrown
2015-04-20 9:27 ` David Howells
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=29536.1428571388@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.