All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wen Gu <guwen@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, davem@davemloft.net, kuba@kernel.org,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/smc: Forward wakeup to smc socket waitqueue after fallback
Date: Mon, 31 Jan 2022 11:20:35 +0000	[thread overview]
Message-ID: <164362803555.29436.10145818429007332261.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1643211184-53645-1-git-send-email-guwen@linux.alibaba.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 26 Jan 2022 23:33:04 +0800 you wrote:
> When we replace TCP with SMC and a fallback occurs, there may be
> some socket waitqueue entries remaining in smc socket->wq, such
> as eppoll_entries inserted by userspace applications.
> 
> After the fallback, data flows over TCP/IP and only clcsocket->wq
> will be woken up. Applications can't be notified by the entries
> which were inserted in smc socket->wq before fallback. So we need
> a mechanism to wake up smc socket->wq at the same time if some
> entries remaining in it.
> 
> [...]

Here is the summary with links:
  - [net] net/smc: Forward wakeup to smc socket waitqueue after fallback
    https://git.kernel.org/netdev/net/c/341adeec9ada

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-01-31 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 15:33 [PATCH net] net/smc: Forward wakeup to smc socket waitqueue after fallback Wen Gu
2022-01-26 15:43 ` Wen Gu
2022-01-31  7:39 ` Karsten Graul
2022-01-31 11:20 ` patchwork-bot+netdevbpf [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=164362803555.29436.10145818429007332261.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=guwen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.