From: "Hanxiao Chen (Fujitsu)" <chenhx.fnst@fujitsu.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
"trond.myklebust@hammerspace.com"
<trond.myklebust@hammerspace.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: 回复: [PATCH 1/1] NFSv4.1: add tracepoint to trunked nfs4_exchange_id calls
Date: Tue, 30 Jan 2024 08:21:41 +0000 [thread overview]
Message-ID: <TYWPR01MB120859F3CB35CAA93D3396C1BE67D2@TYWPR01MB12085.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20240126190333.13528-1-olga.kornievskaia@gmail.com>
> -----邮件原件-----
> 发件人: Olga Kornievskaia <olga.kornievskaia@gmail.com>
> 发送时间: 2024年1月27日 3:04
> 收件人: trond.myklebust@hammerspace.com; anna.schumaker@netapp.com
> 抄送: linux-nfs@vger.kernel.org
> 主题: [PATCH 1/1] NFSv4.1: add tracepoint to trunked nfs4_exchange_id calls
>
> From: Olga Kornievskaia <kolga@netapp.com>
>
> Add a tracepoint to track when the client sends EXCHANGE_ID to test a new
> transport for session trunking.
>
> Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
> ---
> fs/nfs/nfs4proc.c | 3 +++
> fs/nfs/nfs4trace.h | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 33 insertions(+)
>
Tested-by: Chen Hanxiao <chenhx.fnst@fujitsu.com>
Regards,
- Chen
next prev parent reply other threads:[~2024-01-30 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 19:03 [PATCH 1/1] NFSv4.1: add tracepoint to trunked nfs4_exchange_id calls Olga Kornievskaia
2024-01-30 8:21 ` Hanxiao Chen (Fujitsu) [this message]
2024-02-02 13:01 ` Benjamin Coddington
2024-02-02 14:42 ` Olga Kornievskaia
2024-02-02 15:36 ` Benjamin Coddington
[not found] ` <CAN-5tyHjkWsJPteVvLh83X3YTsvvS8vDfHBny-LMaAVbx0ww1g@mail.gmail.com>
2024-02-02 16:56 ` Benjamin Coddington
[not found] ` <CAN-5tyGj_UcFLNkmqqc2bZD218r=Rvxj83_c69T7p9WNi_943Q@mail.gmail.com>
[not found] ` <CAN-5tyEgFnr=NK=mqikC27ixyyORUp5igwtVKDUHs8G2=7bbmA@mail.gmail.com>
2024-02-02 18:24 ` Benjamin Coddington
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=TYWPR01MB120859F3CB35CAA93D3396C1BE67D2@TYWPR01MB12085.jpnprd01.prod.outlook.com \
--to=chenhx.fnst@fujitsu.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--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.