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 v5 4/5] net/smc: Dynamic control auto fallback by socket options
Date: Wed, 9 Feb 2022 08:59:45 +0100 [thread overview]
Message-ID: <e19f2c6a-0429-7e33-4083-caf58414d453@linux.ibm.com> (raw)
In-Reply-To: <9ba496e1-daf1-57d2-318e-bfcd4f57755c@linux.alibaba.com>
On 09/02/2022 07:41, D. Wythe wrote:
>
> Some of our servers have different service types on different ports.
> A global switch cannot control different service ports individually in this case。In fact, it has nothing to do with using netlink or not. Socket options is the first solution comes to my mind in that case，I don't know if there is any other better way。
>
I try to understand why you think it is needed to handle different
service types differently. As you wrote
> After some trial and thought, I found that the scope of netlink control is too large
please explain what you found out. I don't doubt about netlink or socket option here,
its all about why a global switch for this behavior isn't good enough.
next prev parent reply other threads:[~2022-02-09 7:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:53 [PATCH net-next v5 0/5] net/smc: Optimizing performance in short-lived scenarios D. Wythe
2022-02-08 12:53 ` [PATCH net-next v5 1/5] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-08 17:06 ` Karsten Graul
2022-02-09 6:24 ` D. Wythe
2022-02-08 12:53 ` [PATCH net-next v5 2/5] net/smc: Limit backlog connections D. Wythe
2022-02-08 17:13 ` Karsten Graul
2022-02-09 7:11 ` D. Wythe
2022-02-09 7:56 ` Karsten Graul
2022-02-08 12:53 ` [PATCH net-next v5 3/5] net/smc: Fallback when handshake workqueue congested D. Wythe
2022-02-08 12:53 ` [PATCH net-next v5 4/5] net/smc: Dynamic control auto fallback by socket options D. Wythe
2022-02-08 17:08 ` Karsten Graul
2022-02-09 6:41 ` D. Wythe
2022-02-09 7:59 ` Karsten Graul [this message]
2022-02-09 9:01 ` D. Wythe
2022-02-08 12:53 ` [PATCH net-next v5 5/5] net/smc: Add global configure for auto fallback by netlink D. Wythe
2022-02-09 9:16 ` Tony Lu
2022-02-09 9:53 ` D. Wythe
2022-02-09 11:37 ` Tony Lu
2022-02-09 9:33 ` Tony Lu
2022-02-09 9:41 ` D. Wythe
2022-02-09 9:54 ` Tony Lu
2022-02-09 10:56 ` D. Wythe
2022-02-08 17:04 ` [PATCH net-next v5 0/5] net/smc: Optimizing performance in short-lived scenarios Karsten Graul
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=e19f2c6a-0429-7e33-4083-caf58414d453@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