From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
matthieu.baerts@tessares.net
Subject: Re: [PATCH v2 net-next 0/3] net/smc: Optimizing performance in
Date: Wed, 2 Feb 2022 21:00:26 +0800 [thread overview]
Message-ID: <c105a90b-190f-10e5-1100-ff26f2bd6740@linux.alibaba.com> (raw)
In-Reply-To: <83f520b1-d272-cafc-37b1-d086d68f2e9c@linux.ibm.com>
Optimizing performance in short-lived links scenarios...
Sorry for that, it was cut off automatically. I don't know how to keep
it as it was. Could you give me any any suggestions?
Thanks.
在 2022/1/31 下午8:46, Karsten Graul 写道:
> On 28/01/2022 15:44, D. Wythe wrote:
>> From: "D. Wythe" <alibuda@linux.alibaba.com>
>>
>
> Cover letter subject: "Optimizing performance in" ??
prev parent reply other threads:[~2022-02-02 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 14:44 [PATCH v2 net-next 0/3] net/smc: Optimizing performance in D. Wythe
2022-01-28 14:44 ` [PATCH v2 net-next 1/3] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-01-31 12:45 ` Karsten Graul
2022-02-02 12:53 ` D. Wythe
2022-01-28 14:44 ` [PATCH v2 net-next 2/3] net/smc: Limits backlog connections D. Wythe
2022-01-29 4:37 ` Tony Lu
2022-02-02 14:01 ` D. Wythe
2022-01-28 14:44 ` [PATCH v2 net-next 3/3] net/smc: Fallback when handshake workqueue congested D. Wythe
2022-01-29 4:33 ` Tony Lu
2022-02-02 14:04 ` D. Wythe
2022-02-07 7:13 ` D. Wythe
2022-02-07 9:37 ` Tony Lu
2022-01-31 12:46 ` [PATCH v2 net-next 0/3] net/smc: Optimizing performance in Karsten Graul
2022-02-02 13:00 ` 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=c105a90b-190f-10e5-1100-ff26f2bd6740@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=matthieu.baerts@tessares.net \
--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