From: Karsten Graul <kgraul@linux.ibm.com>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/5] net/smc: Optimizing performance in short-lived scenarios
Date: Thu, 10 Feb 2022 15:59:09 +0100 [thread overview]
Message-ID: <7fe9fd06-21cb-1701-d8e7-318b7f29d650@linux.ibm.com> (raw)
In-Reply-To: <cover.1644481811.git.alibuda@linux.alibaba.com>
On 10/02/2022 10:11, D. Wythe wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> This patch set aims to optimizing performance of SMC in short-lived
> links scenarios, which is quite unsatisfactory right now.
This series looks good to me.
Thank you for the valuable contribution to the SMC module and the good discussion!
For the series:
Reviewed-by: Karsten Graul <kgraul@linux.ibm.com>
next prev parent reply other threads:[~2022-02-10 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 9:11 [PATCH net-next v7 0/5] net/smc: Optimizing performance in short-lived scenarios D. Wythe
2022-02-10 9:11 ` [PATCH net-next v7 1/5] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-10 9:11 ` [PATCH net-next v7 2/5] net/smc: Limit backlog connections D. Wythe
2022-02-10 9:11 ` [PATCH net-next v7 3/5] net/smc: Limit SMC visits when handshake workqueue congested D. Wythe
2022-02-10 9:11 ` [PATCH net-next v7 4/5] net/smc: Dynamic control handshake limitation by socket options D. Wythe
2022-02-10 9:11 ` [PATCH net-next v7 5/5] net/smc: Add global configure for handshake limitation by netlink D. Wythe
2022-02-11 2:46 ` Tony Lu
2022-02-10 14:59 ` Karsten Graul [this message]
2022-02-11 9:41 ` [PATCH net-next v7 0/5] net/smc: Optimizing performance in short-lived scenarios D. Wythe
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=7fe9fd06-21cb-1701-d8e7-318b7f29d650@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox