From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>,
kgraul@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: [net-next v7 0/4] net/smc: optimize the parallelism of SMC-R connections
Date: Mon, 6 Feb 2023 20:11:59 +0800 [thread overview]
Message-ID: <93bc1405-2f76-54b6-bae3-39da4542e618@linux.alibaba.com> (raw)
In-Reply-To: <273e8c67-fbb0-edd8-600f-512c1a6812f3@linux.ibm.com>
On 2/6/23 7:06 PM, Wenjia Zhang wrote:
>
>
> On 02.02.23 09:26, D. Wythe wrote:
>> From: "D. Wythe" <alibuda@linux.alibaba.com>
>>
> This answer seems too late ;-)
>
> I did some test as thoroughly as I can, it looks good to me.
>
> Reviewed-by: Wenjia Zhang <wenjia@linux.ibm.com>
Hi, wenjia
Thank you very much for your test. I'm very glad that you it passed.
I will resend those as soon as possible. (make confirm/delete rkey process concurrently)
Best wishes.
D. Wythe
prev parent reply other threads:[~2023-02-06 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 8:26 [net-next v7 0/4] net/smc: optimize the parallelism of SMC-R connections D. Wythe
2023-02-02 8:26 ` [net-next v7 1/4] net/smc: llc_conf_mutex refactor, replace it with rw_semaphore D. Wythe
2023-02-02 8:26 ` [net-next v7 2/4] net/smc: use read semaphores to reduce unnecessary blocking in smc_buf_create() & smcr_buf_unuse() D. Wythe
2023-02-02 8:26 ` [net-next v7 3/4] net/smc: reduce unnecessary blocking in smcr_lgr_reg_rmbs() D. Wythe
2023-02-02 8:26 ` [net-next v7 4/4] net/smc: replace mutex rmbs_lock and sndbufs_lock with rw_semaphore D. Wythe
2023-02-03 17:36 ` [net-next v7 0/4] net/smc: optimize the parallelism of SMC-R connections Wenjia Zhang
2023-02-06 11:06 ` Wenjia Zhang
2023-02-06 12:11 ` D. Wythe [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=93bc1405-2f76-54b6-bae3-39da4542e618@linux.alibaba.com \
--to=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).