From: justin <jlec@gentoo.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Suresh Jayaraman <sjayaraman@suse.com>,
David Howells <dhowells@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-cachefs@redhat.com
Subject: Re: [PATCH] [RESEND] fs: cachefiles: Add support for large files in filesystem caching
Date: Tue, 19 Jun 2012 09:58:43 +0200 [thread overview]
Message-ID: <4FE03133.6070606@gentoo.org> (raw)
In-Reply-To: <20120619005214.989e90a8.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On 19/06/12 09:52, Andrew Morton wrote:
> On Tue, 19 Jun 2012 10:57:27 +0530 Suresh Jayaraman <sjayaraman@suse.com> wrote:
>
>>> How extensively was this change tested? Please describe the testing
>>> which was performed?
>>>
>>
>> The original patch was tested by mounting a NFS share with fscache
>> option enabled, do a md5sum on a nfs file larger than 2GB and ensure
>> that the file is getting cached by fscache (watch cache size growing)
>> on x86_64.
>
> Well it will need a lot more coverage testing than that. truncate?
> expanding truncate? write, lseek, pwrite, pread(), mmap(MAP_SHARED),
> behavior at the new max file size (what is that?), etc.
>
Hello,
I am using this patch since the 2.6.3* linux, while working with files
>4 Gb on a daily bases. This isn't a testsuite, but it worked fine for
me all the time.
How would such testsuite you request look like? Anybody willing to write it?
Thanks,
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 302 bytes --]
next prev parent reply other threads:[~2012-06-19 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 5:38 [PATCH] [RESEND] fs: cachefiles: Add support for large files in filesystem caching Suresh Jayaraman
2012-06-18 23:04 ` Andrew Morton
2012-06-19 5:27 ` Suresh Jayaraman
2012-06-19 7:52 ` Andrew Morton
2012-06-19 7:58 ` justin [this message]
2012-06-20 13:35 ` Suresh Jayaraman
2012-06-20 19:45 ` Justin
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=4FE03133.6070606@gentoo.org \
--to=jlec@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.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