From: patchwork-bot+netdevbpf@kernel.org
To: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
Cc: stefanha@redhat.com, sgarzare@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mst@redhat.com, jasowang@redhat.com,
bobby.eshleman@bytedance.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@sberdevices.ru, oxffffaa@gmail.com,
avkrasnov@sberdevices.ru
Subject: Re: [PATCH net-next v3 0/4] virtio/vsock: some updates for MSG_PEEK flag
Date: Thu, 27 Jul 2023 14:00:24 +0000 [thread overview]
Message-ID: <169046642452.7106.8460568966889675148.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725172912.1659970-1-AVKrasnov@sberdevices.ru>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 25 Jul 2023 20:29:08 +0300 you wrote:
> Hello,
>
> This patchset does several things around MSG_PEEK flag support. In
> general words it reworks MSG_PEEK test and adds support for this flag
> in SOCK_SEQPACKET logic. Here is per-patch description:
>
> 1) This is cosmetic change for SOCK_STREAM implementation of MSG_PEEK:
> 1) I think there is no need of "safe" mode walk here as there is no
> "unlink" of skbs inside loop (it is MSG_PEEK mode - we don't change
> queue).
> 2) Nested while loop is removed: in case of MSG_PEEK we just walk
> over skbs and copy data from each one. I guess this nested loop
> even didn't behave as loop - it always executed just for single
> iteration.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] virtio/vsock: rework MSG_PEEK for SOCK_STREAM
https://git.kernel.org/netdev/net-next/c/051e77e33946
- [net-next,v3,2/4] virtio/vsock: support MSG_PEEK for SOCK_SEQPACKET
https://git.kernel.org/netdev/net-next/c/a75f501de88e
- [net-next,v3,3/4] vsock/test: rework MSG_PEEK test for SOCK_STREAM
https://git.kernel.org/netdev/net-next/c/587ed79f62a7
- [net-next,v3,4/4] vsock/test: MSG_PEEK test for SOCK_SEQPACKET
https://git.kernel.org/netdev/net-next/c/8a0697f23e5a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-27 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 17:29 [PATCH net-next v3 0/4] virtio/vsock: some updates for MSG_PEEK flag Arseniy Krasnov
2023-07-25 17:29 ` [PATCH net-next v3 1/4] virtio/vsock: rework MSG_PEEK for SOCK_STREAM Arseniy Krasnov
2023-07-25 17:29 ` [PATCH net-next v3 2/4] virtio/vsock: support MSG_PEEK for SOCK_SEQPACKET Arseniy Krasnov
2023-07-25 17:29 ` [PATCH net-next v3 3/4] vsock/test: rework MSG_PEEK test for SOCK_STREAM Arseniy Krasnov
2023-07-25 17:29 ` [PATCH net-next v3 4/4] vsock/test: MSG_PEEK test for SOCK_SEQPACKET Arseniy Krasnov
2023-07-26 8:04 ` Stefano Garzarella
2023-07-26 10:02 ` [PATCH net-next v3 0/4] virtio/vsock: some updates for MSG_PEEK flag Michael S. Tsirkin
2023-07-27 14:00 ` 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=169046642452.7106.8460568966889675148.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@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=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).