linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	Tony Lu <tonylu@linux.alibaba.com>
Subject: Re: [PATCH net-next v4 3/3] net/smc: Fallback when handshake workqueue congested
Date: Tue, 8 Feb 2022 20:58:04 +0800	[thread overview]
Message-ID: <df0a98b0-9e27-013a-cdeb-1ebcade043bf@linux.alibaba.com> (raw)
In-Reply-To: <7d18c7ac-9a4f-6a4f-2acf-5c83112fe967@linux.ibm.com>


You may have misunderstood what I mean ... but it doesn't matter now, 
I've sent the v5 series.

Looking forward to your suggestions for v5 series.

Thanks.

在 2022/2/7 下午6:03, Karsten Graul 写道:
> On 07/02/2022 10:50, D. Wythe wrote:
>>
>> The main communication in v2 series is about adding a dynamic control for auto fallback to TCP. I will soon add a new patch to implements this in v5 series, or modify it in curret patch. Which one do you recommend?
>>
> 
> When you change a patch then you need to send a new series.

      reply	other threads:[~2022-02-08 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  6:24 [PATCH net-next v4 0/3] net/smc: Optimizing performance in short-lived scenarios D. Wythe
2022-02-07  6:24 ` [PATCH net-next v4 1/3] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-07  6:24 ` [PATCH net-next v4 2/3] net/smc: Limits backlog connections D. Wythe
2022-02-07  6:24 ` [PATCH net-next v4 3/3] net/smc: Fallback when handshake workqueue congested D. Wythe
2022-02-07  7:56   ` Karsten Graul
2022-02-07  9:50     ` D. Wythe
2022-02-07 10:03       ` Karsten Graul
2022-02-08 12:58         ` 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=df0a98b0-9e27-013a-cdeb-1ebcade043bf@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=netdev@vger.kernel.org \
    --cc=tonylu@linux.alibaba.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).