From: patchwork-bot+netdevbpf@kernel.org
To: Tony Lu <tonylu@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, kuba@kernel.org, davem@davemloft.net,
guwen@linux.alibaba.com, dust.li@linux.alibaba.com,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Tracepoints for SMC
Date: Mon, 01 Nov 2021 13:50:07 +0000 [thread overview]
Message-ID: <163577460757.13123.13168194829580546848.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211101073912.60410-1-tonylu@linux.alibaba.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 1 Nov 2021 15:39:10 +0800 you wrote:
> This patch set introduces tracepoints for SMC, including the tracepoints
> basic code. The tracepoitns would help us to track SMC's behaviors by
> automatic tools, or other BPF tools, and zero overhead if not enabled.
>
> Compared with kprobe and other dymatic tools, the tracepoints are
> considered as stable API, and less overhead for tracing with easy-to-use
> API.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net/smc: Introduce tracepoint for fallback
https://git.kernel.org/netdev/net-next/c/482626086820
- [net-next,2/3] net/smc: Introduce tracepoints for tx and rx msg
https://git.kernel.org/netdev/net-next/c/aff3083f10bf
- [net-next,3/3] net/smc: Introduce tracepoint for smcr link down
https://git.kernel.org/netdev/net-next/c/a3a0e81b6fd5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-01 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 7:39 [PATCH net-next 0/3] Tracepoints for SMC Tony Lu
2021-11-01 7:39 ` [PATCH net-next 1/3] net/smc: Introduce tracepoint for fallback Tony Lu
2021-11-01 7:39 ` [PATCH net-next 2/3] net/smc: Introduce tracepoints for tx and rx msg Tony Lu
2021-11-01 7:39 ` [PATCH net-next 3/3] net/smc: Introduce tracepoint for smcr link down Tony Lu
2021-11-02 9:30 ` Karsten Graul
2021-11-03 6:57 ` Tony Lu
2021-11-01 13:50 ` patchwork-bot+netdevbpf [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=163577460757.13123.13168194829580546848.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=guwen@linux.alibaba.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.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.