MIME-Version: 1.0
References: <164021479106.640689.17404516570194656552.stgit@warthog.procyon.org.uk>
In-Reply-To: <164021479106.640689.17404516570194656552.stgit@warthog.procyon.org.uk>
From:   Daire Byrne <daire@dneg.com>
Date:   Mon, 10 Jan 2022 11:51:54 +0000
Message-ID: <CAPt2mGNt0shT7xmvCKb-G+gpza_eTrVqPhcVGx_7+smtGOHECw@mail.gmail.com>
Subject: Re: [PATCH v4 00/68] fscache, cachefiles: Rewrite
To:     David Howells <dhowells@redhat.com>
Cc:     linux-cachefs@redhat.com, Jeff Layton <jlayton@kernel.org>,
        Dave Wysochanski <dwysocha@redhat.com>,
        Anna Schumaker <Anna.Schumaker@netapp.com>,
        Trond Myklebust <trond.myklebust@hammerspace.com>,
        linux-nfs@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 22 Dec 2021 at 23:13, David Howells <dhowells@redhat.com> wrote:
> These patches can be found also on:
>
>         https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-rewrite

I have run this through our production workloads without issue. There
were no recorded performance or stability differences between this and
the old fscache/cachefiles.

Our workload comprises mounting ~20 remote servers with "-o fsc" over
the WAN and then re-exporting those to 500 local client instances.
This production workload churns the fscache backing filesystem (EXT4)
pretty well (hundreds of MB/s) across all of the mount points
simultaneously.

I tested with both NFSv4.2 and NFSv3 mounts. Previously written cache
data was correctly reused between reboots and remounts.

Tested-by: Daire Byrne <daire@dneg.com>

Cheers,

Daire