From: Calum Mackay <calum.mackay@oracle.com>
To: Martin Wege <martin.l.wege@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Calum Mackay <calum.mackay@oracle.com>
Subject: Re: Filesystem test suite for NFSv4?
Date: Tue, 30 Jan 2024 01:22:06 +0000 [thread overview]
Message-ID: <99ec805e-a0d4-44ea-a6ea-9478e98d4670@oracle.com> (raw)
In-Reply-To: <CANH4o6PxoQEk3SFvRDa+BqpKXFUW6cPC9Jcuf886Ntxqmorbmw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
hi Martin,
On 29/01/2024 11:43 pm, Martin Wege wrote:
> On Thu, Nov 16, 2023 at 10:26 PM Martin Wege <martin.l.wege@gmail.com> wrote:
>>
>> On Thu, Nov 16, 2023 at 8:55 AM Mkrtchyan, Tigran
>> <tigran.mkrtchyan@desy.de> wrote:
>>>
>>>
>>> What do you want to test?
>>
>> Filesystem tests, from POSIX layer. open(), close(), mmap(), write(),
>> read(), SEEK_HOLE, SEEK_DATA
>>
>>> Protocol-level test can be performed with pynfs:
>>>
>>> https://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=summary
>>>
>>> IO bandwidth and latency tests can be performed ior or fio.
>>
>> Is this a test for the NFS server, or NFS client?
It is mostly tests of the server, via sending hand-rolled protocol
calls, although there is some limited support for testing a client.
best wishes,
calum.
>>
>> Thanks,
>> Martin
>
> ?
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-01-30 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 7:42 Filesystem test suite for NFSv4? Martin Wege
2023-11-16 7:05 ` Martin Wege
2023-11-16 7:55 ` Mkrtchyan, Tigran
2023-11-16 14:36 ` Chuck Lever III
2023-11-16 21:26 ` Martin Wege
2024-01-29 23:43 ` Martin Wege
2024-01-30 1:22 ` Calum Mackay [this message]
2024-01-31 14:40 ` Olga Kornievskaia
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=99ec805e-a0d4-44ea-a6ea-9478e98d4670@oracle.com \
--to=calum.mackay@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.l.wege@gmail.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;
as well as URLs for NNTP newsgroup(s).