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 v6 5/5] net/smc: Add global configure for auto fallback by netlink
Date: Wed, 9 Feb 2022 17:21:35 +0100 [thread overview]
Message-ID: <1a1a740c-7dcf-4921-0a05-a727e2a5170e@linux.ibm.com> (raw)
In-Reply-To: <64348e3dcd0b74ed638e895fa217d03df9bec854.1644413637.git.alibuda@linux.alibaba.com>
On 09/02/2022 15:11, D. Wythe wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> Although we can control SMC auto fallback through socket options, which
> means that applications who need it must modify their code. It's quite
> troublesome for many existing applications. This patch modifies the
> global default value of auto fallback through netlink, providing a way
> to auto fallback without modifying any code for applications.
>
And of course also in this patch: no "auto fallback" in comments or as part
of variable names.
Do you plan to enhance the smc-tools user space part, too?
next prev parent reply other threads:[~2022-02-09 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 14:11 [PATCH net-next v6 0/5] net/smc: Optimizing performance in short-lived scenarios D. Wythe
2022-02-09 14:11 ` [PATCH net-next v6 1/5] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-09 14:11 ` [PATCH net-next v6 2/5] net/smc: Limit backlog connections D. Wythe
2022-02-09 16:02 ` Karsten Graul
2022-02-10 3:28 ` D. Wythe
2022-02-09 14:11 ` [PATCH net-next v6 3/5] net/smc: Fallback when handshake workqueue congested D. Wythe
2022-02-09 16:11 ` Karsten Graul
2022-02-10 3:43 ` D. Wythe
2022-02-09 14:11 ` [PATCH net-next v6 4/5] net/smc: Dynamic control auto fallback by socket options D. Wythe
2022-02-09 16:20 ` Karsten Graul
2022-02-09 14:11 ` [PATCH net-next v6 5/5] net/smc: Add global configure for auto fallback by netlink D. Wythe
2022-02-09 16:21 ` Karsten Graul [this message]
2022-02-10 3:47 ` 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=1a1a740c-7dcf-4921-0a05-a727e2a5170e@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