From: Wen Gu <guwen@linux.alibaba.com>
To: dust.li@linux.alibaba.com, kgraul@linux.ibm.com,
davem@davemloft.net, kuba@kernel.org
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/smc: Send out the remaining data in sndbuf before close
Date: Mon, 28 Mar 2022 17:55:59 +0800 [thread overview]
Message-ID: <da663f43-a593-6acc-d4ec-9bd932637bee@linux.alibaba.com> (raw)
In-Reply-To: <20220328090411.GI35207@linux.alibaba.com>
Thanks for your comments.
On 2022/3/28 5:04 pm, dust.li wrote:
>
> I think this issue should also happen if TCP_CORK is set and
> autocorking is not enabled ?
Yes, setting TCP_CORK also works.
>
> Autocorking and delaying the TX from BH to smc_release_cb() greatly
> increased the probability of this problem.
>
Thanks,
Wen Gu
next prev parent reply other threads:[~2022-03-28 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 6:10 [PATCH net] net/smc: Send out the remaining data in sndbuf before close Wen Gu
2022-03-28 9:04 ` dust.li
2022-03-28 9:55 ` Wen Gu [this message]
2022-03-28 10:02 ` Karsten Graul
2022-03-28 23:30 ` patchwork-bot+netdevbpf
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=da663f43-a593-6acc-d4ec-9bd932637bee@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@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