From: Alexandra Winter <wintera@linux.ibm.com>
To: "D. Wythe" <alibuda@linux.alibaba.com>,
kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [RFC net-next 0/2] Optimize the parallelism of SMC-R connections
Date: Tue, 26 Sep 2023 09:37:47 +0200 [thread overview]
Message-ID: <d488ff86-8b99-e669-dfbf-ee05bb7b1536@linux.ibm.com> (raw)
In-Reply-To: <a3e80a67-e8b8-ce94-fc11-254d056d37a9@linux.alibaba.com>
On 25.09.23 12:10, D. Wythe wrote:
> That's right. But even if we do nothing, the current implements still has this problem.
> And this problem can be solved by the spinlock inside smc_conn_create, rather than the
> pending lock.
>
May I kindly propose to fix this problem first and then do performance improvements after that?
> And also deleting the last connection from a link group will not shutting the down right now,
> usually waiting for 10 minutes of idle time.
Still the new connection could come in just the moment when the 10 minutes are over.
prev parent reply other threads:[~2023-09-26 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 13:55 [RFC net-next 0/2] Optimize the parallelism of SMC-R connections D. Wythe
2023-09-06 13:55 ` [RFC net-next 1/2] net/smc: refactoring lgr pending lock D. Wythe
2023-09-06 13:55 ` [RFC net-next 2/2] net/smc: remove locks smc_client_lgr_pending and smc_server_lgr_pending D. Wythe
2023-09-08 9:07 ` [RFC net-next 0/2] Optimize the parallelism of SMC-R connections Alexandra Winter
[not found] ` <522d823c-b656-ffb5-bcce-65b96bdfa46d@linux.alibaba.com>
2023-09-21 12:36 ` Alexandra Winter
2023-09-25 10:10 ` D. Wythe
2023-09-26 7:37 ` Alexandra Winter [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=d488ff86-8b99-e669-dfbf-ee05bb7b1536@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=jaka@linux.ibm.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=wenjia@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).