From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] nfs_lib.sh: Set NFS 4.2 on TCP as the default
Date: Fri, 29 Sep 2023 13:26:13 +0200 [thread overview]
Message-ID: <20230929112613.GA379979@pevik> (raw)
In-Reply-To: <20230721123852.1420080-1-pvorel@suse.cz>
Hi all,
> Previously NFS 3 on UDP was the default, which leaded to test being
> skipped when tests run without parameters:
> TCONF: UDP support disabled on NFS server
> This does not have an effect when tests run properly via
> runtest/net.nfs, which specify parameters. It just safes typing
> -t tcp (and optionally -v 4.2) when one runs single test manually.
FYI patch merged.
Kind regards,
Petr
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi,
> I'm pretty sure, we don't want to have UDP as the default (besides
> skipped with TCONF it was acked by Jeff [1]). But I wonder if NFS 4.2 is
> the best as the default version. Maybe just 4 or 4.1?
> Kind regards,
> Petr
> [1] https://lore.kernel.org/ltp/e4d22ae6cefb34463ed7d04287ca9e81cd0949d8.camel@kernel.org/
> testcases/network/nfs/nfs_stress/nfs_lib.sh | 4 ++--
...
> -VERSION=${VERSION:=3}
> +VERSION=${VERSION:=4.2}
> NFILES=${NFILES:=1000}
> -SOCKET_TYPE="${SOCKET_TYPE:-udp}"
> +SOCKET_TYPE="${SOCKET_TYPE:-tcp}"
prev parent reply other threads:[~2023-09-29 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 12:38 [PATCH 1/1] nfs_lib.sh: Set NFS 4.2 on TCP as the default Petr Vorel
2023-09-29 11:26 ` Petr Vorel [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=20230929112613.GA379979@pevik \
--to=pvorel@suse.cz \
--cc=Anna.Schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=olga.kornievskaia@gmail.com \
--cc=trond.myklebust@hammerspace.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).