All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: ltp@lists.linux.it,
	Olga Kornievskaia <olga.kornievskaia@gmail.com>,
	Anna Schumaker <Anna.Schumaker@netapp.com>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] runtest/net.nfs: Run nfs02_06 on TCP only
Date: Wed, 12 Jul 2023 13:18:18 +0200	[thread overview]
Message-ID: <20230712111818.GA775074@pevik> (raw)
In-Reply-To: <e4d22ae6cefb34463ed7d04287ca9e81cd0949d8.camel@kernel.org>

Hi Jeff,

> On Thu, 2023-06-22 at 10:46 +0200, Petr Vorel wrote:
> > UDP support disabled was on NFS server in kernel 5.6.
> > Due that 2 of 3 nfs06.sh tests runs are being skipped on newer kernels.

> > Therefore NFSv3 job in nfs02_06 test as TCP. This way all jobs in the
> > test are TCP, thus test will not be skipped. This also bring NFSv3
> > testing also under TCP (previously it was tested only on UDP).

> > Keep UDP in nfs01_06 jobs, so that NFSv3 on UDP is still covered for
> > older kernels.

> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> >  runtest/net.nfs | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)

> > diff --git a/runtest/net.nfs b/runtest/net.nfs
> > index 72cf4b307..15a960017 100644
> > --- a/runtest/net.nfs
> > +++ b/runtest/net.nfs
> > @@ -58,7 +58,7 @@ nfs41_ipv6_05 nfs05.sh -6 -v 4.1 -t tcp
> >  nfs42_ipv6_05 nfs05.sh -6 -v 4.2 -t tcp

> >  nfs01_06  nfs06.sh -v "3,3,3,4,4,4" -t "udp,udp,tcp,tcp,tcp,tcp"
> > -nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "udp,tcp,tcp,tcp,tcp,tcp"
> > +nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"
> >  nfs03_ipv6_06 nfs06.sh -6 -v "4,4.1,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"

> >  nfs3_07 nfs07.sh -v 3 -t udp

> UDP support is more or less being deprecated at this point, so testing
> on tcp is preferred.

> Acked-by: Jeff Layton <jlayton@kernel.org>

too late to add the ack to the commit message (already merged),
but thanks for your confirmation.

FYI I kept some UDP testing because new LTP releases are sometimes used with
*not so old* enterprise distros. But these UDP tests are single tests (there is
one test run under TCP and one under UDP). nfs06.sh is specific that it combines
6 various NFS versions and TCP + UDP, and single UDP causes whole specific test
run being cancelled. And again, I still kept nfs01_06 which uses older NFS (ver
3 and 4) with original UDP for older distros.

Interesting question is when to drop UDP testing completely. I guess few years
after kernel 5.6 was released, when all major enterprise distros are based on
kernel >= 5.6 and there are no stable/LTS with older kernel (e.g. in 2026, when
5.4 and older LTS will be EOL).

Kind regards,
Petr

WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
	linux-nfs@vger.kernel.org,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Anna Schumaker <Anna.Schumaker@netapp.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] runtest/net.nfs: Run nfs02_06 on TCP only
Date: Wed, 12 Jul 2023 13:18:18 +0200	[thread overview]
Message-ID: <20230712111818.GA775074@pevik> (raw)
In-Reply-To: <e4d22ae6cefb34463ed7d04287ca9e81cd0949d8.camel@kernel.org>

Hi Jeff,

> On Thu, 2023-06-22 at 10:46 +0200, Petr Vorel wrote:
> > UDP support disabled was on NFS server in kernel 5.6.
> > Due that 2 of 3 nfs06.sh tests runs are being skipped on newer kernels.

> > Therefore NFSv3 job in nfs02_06 test as TCP. This way all jobs in the
> > test are TCP, thus test will not be skipped. This also bring NFSv3
> > testing also under TCP (previously it was tested only on UDP).

> > Keep UDP in nfs01_06 jobs, so that NFSv3 on UDP is still covered for
> > older kernels.

> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> >  runtest/net.nfs | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)

> > diff --git a/runtest/net.nfs b/runtest/net.nfs
> > index 72cf4b307..15a960017 100644
> > --- a/runtest/net.nfs
> > +++ b/runtest/net.nfs
> > @@ -58,7 +58,7 @@ nfs41_ipv6_05 nfs05.sh -6 -v 4.1 -t tcp
> >  nfs42_ipv6_05 nfs05.sh -6 -v 4.2 -t tcp

> >  nfs01_06  nfs06.sh -v "3,3,3,4,4,4" -t "udp,udp,tcp,tcp,tcp,tcp"
> > -nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "udp,tcp,tcp,tcp,tcp,tcp"
> > +nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"
> >  nfs03_ipv6_06 nfs06.sh -6 -v "4,4.1,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"

> >  nfs3_07 nfs07.sh -v 3 -t udp

> UDP support is more or less being deprecated at this point, so testing
> on tcp is preferred.

> Acked-by: Jeff Layton <jlayton@kernel.org>

too late to add the ack to the commit message (already merged),
but thanks for your confirmation.

FYI I kept some UDP testing because new LTP releases are sometimes used with
*not so old* enterprise distros. But these UDP tests are single tests (there is
one test run under TCP and one under UDP). nfs06.sh is specific that it combines
6 various NFS versions and TCP + UDP, and single UDP causes whole specific test
run being cancelled. And again, I still kept nfs01_06 which uses older NFS (ver
3 and 4) with original UDP for older distros.

Interesting question is when to drop UDP testing completely. I guess few years
after kernel 5.6 was released, when all major enterprise distros are based on
kernel >= 5.6 and there are no stable/LTS with older kernel (e.g. in 2026, when
5.4 and older LTS will be EOL).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-07-12 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22  8:46 [PATCH 1/1] runtest/net.nfs: Run nfs02_06 on TCP only Petr Vorel
2023-06-22  8:46 ` [LTP] " Petr Vorel
2023-07-12  7:51 ` Cyril Hrubis
2023-07-12  7:51   ` Cyril Hrubis
2023-07-12  8:37   ` Petr Vorel
2023-07-12  8:37     ` Petr Vorel
2023-07-12 10:28 ` Jeff Layton
2023-07-12 10:28   ` [LTP] " Jeff Layton
2023-07-12 11:18   ` Petr Vorel [this message]
2023-07-12 11:18     ` Petr Vorel

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=20230712111818.GA775074@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 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.