All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: copy_file_range() infinitely hangs on NFSv4.2 over RDMA
Date: Tue, 16 Feb 2021 23:27:23 +0100	[thread overview]
Message-ID: <0e49471c-e640-a331-c7b4-4e0a49a7a967@rothenpieler.org> (raw)
In-Reply-To: <81cb9aef-c10d-f11c-42c0-5144ee2608bc@rothenpieler.org>


[-- Attachment #1.1: Type: text/plain, Size: 525 bytes --]

On 16.02.2021 21:37, Timo Rothenpieler wrote:
> I can't get a network (I assume just TCP/20049 is fine, and not also 
> some RDMA trace?) right now, but I will once a user has finished their 
> work on the machine.

There wasn't any TCP traffic to dump on the NFSoRDMA Port, probably 
because everything is handled via RDMA/IB.
But I recorded a trace log of rpcrdma and sunrpc observing the situation.

To me it looks like the COPY task (task:15886@7) completes successfully?
The compressed trace.dat is attached.

[-- Attachment #1.2: trace.dat.xz --]
[-- Type: application/octet-stream, Size: 558188 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4494 bytes --]

  reply	other threads:[~2021-02-16 22:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14  3:31 copy_file_range() infinitely hangs on NFSv4.2 over RDMA Timo Rothenpieler
2021-02-16 20:12 ` Olga Kornievskaia
2021-02-16 20:37   ` Timo Rothenpieler
2021-02-16 22:27     ` Timo Rothenpieler [this message]
2021-02-17 22:37       ` Olga Kornievskaia
2021-02-18  1:12         ` Timo Rothenpieler
2021-02-18  3:52           ` Olga Kornievskaia
2021-02-18 13:28             ` Timo Rothenpieler
2021-02-18 15:55               ` Timo Rothenpieler
2021-02-18 18:30                 ` Olga Kornievskaia
2021-02-18 20:22                   ` Timo Rothenpieler
2021-02-19 17:38                     ` Olga Kornievskaia
2021-02-19 17:48                       ` Chuck Lever
2021-02-19 18:01                         ` Timo Rothenpieler
2021-02-19 18:48                           ` Chuck Lever
2021-02-19 20:37                             ` Timo Rothenpieler
2021-02-19 20:43                             ` Olga Kornievskaia
2021-02-19 20:55                               ` Chuck Lever
2021-02-20 21:03                             ` Timo Rothenpieler
2021-02-21 17:45                               ` Chuck Lever

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=0e49471c-e640-a331-c7b4-4e0a49a7a967@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --cc=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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.