From: patchwork-bot+netdevbpf@kernel.org
To: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kys@microsoft.com,
haiyangz@microsoft.com, sthemmin@microsoft.com,
wei.liu@kernel.org, decui@microsoft.com, stefanha@redhat.com,
bryantan@vmware.com, vdasa@vmware.com, oxffffaa@gmail.com,
mst@redhat.com, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, kvm@vger.kernel.org,
kernel@sberdevices.ru, pv-drivers@vmware.com
Subject: Re: [PATCH net-next v4 0/9] vsock: updates for SO_RCVLOWAT handling
Date: Tue, 23 Aug 2022 09:20:17 +0000 [thread overview]
Message-ID: <166124641741.3613.14462529402245081458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <de41de4c-0345-34d7-7c36-4345258b7ba8@sberdevices.ru>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 19 Aug 2022 05:21:58 +0000 you wrote:
> Hello,
>
> This patchset includes some updates for SO_RCVLOWAT:
>
> 1) af_vsock:
> During my experiments with zerocopy receive, i found, that in some
> cases, poll() implementation violates POSIX: when socket has non-
> default SO_RCVLOWAT(e.g. not 1), poll() will always set POLLIN and
> POLLRDNORM bits in 'revents' even number of bytes available to read
> on socket is smaller than SO_RCVLOWAT value. In this case,user sees
> POLLIN flag and then tries to read data(for example using 'read()'
> call), but read call will be blocked, because SO_RCVLOWAT logic is
> supported in dequeue loop in af_vsock.c. But the same time, POSIX
> requires that:
>
> [...]
Here is the summary with links:
- [net-next,v4,1/9] vsock: SO_RCVLOWAT transport set callback
https://git.kernel.org/netdev/net-next/c/e38f22c860ed
- [net-next,v4,2/9] hv_sock: disable SO_RCVLOWAT support
https://git.kernel.org/netdev/net-next/c/24764f8d3c31
- [net-next,v4,3/9] virtio/vsock: use 'target' in notify_poll_in callback
https://git.kernel.org/netdev/net-next/c/e7a3266c9167
- [net-next,v4,4/9] vmci/vsock: use 'target' in notify_poll_in callback
https://git.kernel.org/netdev/net-next/c/a274f6ff3c5c
- [net-next,v4,5/9] vsock: pass sock_rcvlowat to notify_poll_in as target
https://git.kernel.org/netdev/net-next/c/ee0b3843a269
- [net-next,v4,6/9] vsock: add API call for data ready
https://git.kernel.org/netdev/net-next/c/f2fdcf67aceb
- [net-next,v4,7/9] virtio/vsock: check SO_RCVLOWAT before wake up reader
https://git.kernel.org/netdev/net-next/c/39f1ed33a448
- [net-next,v4,8/9] vmci/vsock: check SO_RCVLOWAT before wake up reader
https://git.kernel.org/netdev/net-next/c/e061aed99855
- [net-next,v4,9/9] vsock_test: POLLIN + SO_RCVLOWAT test
https://git.kernel.org/netdev/net-next/c/b1346338fbae
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-23 11:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 5:21 [PATCH net-next v4 0/9] vsock: updates for SO_RCVLOWAT handling Arseniy Krasnov
2022-08-19 5:25 ` [PATCH net-next v4 1/9] vsock: SO_RCVLOWAT transport set callback Arseniy Krasnov
2022-08-19 5:27 ` [PATCH net-next v4 2/9] hv_sock: disable SO_RCVLOWAT support Arseniy Krasnov
2022-08-19 5:29 ` [PATCH net-next v4 3/9] virtio/vsock: use 'target' in notify_poll_in callback Arseniy Krasnov
2022-08-19 5:31 ` [PATCH net-next v4 4/9] vmci/vsock: " Arseniy Krasnov
2022-08-19 5:33 ` [PATCH net-next v4 5/9] vsock: pass sock_rcvlowat to notify_poll_in as target Arseniy Krasnov
2022-08-19 5:36 ` [PATCH net-next v4 6/9] vsock: add API call for data ready Arseniy Krasnov
2022-08-19 5:39 ` [PATCH net-next v4 7/9] virtio/vsock: check SO_RCVLOWAT before wake up reader Arseniy Krasnov
2022-08-19 5:41 ` [PATCH net-next v4 8/9] vmci/vsock: " Arseniy Krasnov
2022-08-19 5:43 ` [PATCH net-next v4 9/9] vsock_test: POLLIN + SO_RCVLOWAT test Arseniy Krasnov
2022-08-23 9:20 ` patchwork-bot+netdevbpf [this message]
2022-08-23 19:14 ` [PATCH net-next v4 0/9] vsock: updates for SO_RCVLOWAT handling Stefan Hajnoczi
2022-08-23 19:14 ` Stefan Hajnoczi
2022-08-23 19:18 ` Jakub Kicinski
2022-08-23 20:30 ` Stefan Hajnoczi
2022-08-23 20:30 ` Stefan Hajnoczi
2022-08-23 20:57 ` Paolo Abeni
2022-08-23 20:57 ` Paolo Abeni
2022-08-24 3:48 ` Arseniy Krasnov
2022-08-29 13:52 ` Stefano Garzarella
2022-08-29 13:52 ` Stefano Garzarella
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=166124641741.3613.14462529402245081458.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=bryantan@vmware.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=pv-drivers@vmware.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=vdasa@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.liu@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.