From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, stefanha@redhat.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/5] vsock: SOCK_LINGER rework
Date: Tue, 27 May 2025 09:50:34 +0000 [thread overview]
Message-ID: <174833943425.1235580.6276796573046054337.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250522-vsock-linger-v6-0-2ad00b0e447e@rbox.co>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 22 May 2025 01:18:20 +0200 you wrote:
> Change vsock's lingerning to wait on close() until all data is sent, i.e.
> until workers picked all the packets for processing.
>
> Changes in v6:
> - Make vsock_wait_sent() return bool, parametrize enable_so_linger() with
> timeout, don't open code DIV_ROUND_UP [Stefano]
> - Link to v5: https://lore.kernel.org/r/20250521-vsock-linger-v5-0-94827860d1d6@rbox.co
>
> [...]
Here is the summary with links:
- [net-next,v6,1/5] vsock/virtio: Linger on unsent data
https://git.kernel.org/netdev/net-next/c/1c39f5dbbfd2
- [net-next,v6,2/5] vsock: Move lingering logic to af_vsock core
https://git.kernel.org/netdev/net-next/c/5ec40864aaec
- [net-next,v6,3/5] vsock/test: Introduce vsock_wait_sent() helper
https://git.kernel.org/netdev/net-next/c/e78e0596c762
- [net-next,v6,4/5] vsock/test: Introduce enable_so_linger() helper
https://git.kernel.org/netdev/net-next/c/8b07b7e5c253
- [net-next,v6,5/5] vsock/test: Add test for an unexpectedly lingering close()
https://git.kernel.org/netdev/net-next/c/393d070135ad
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:[~2025-05-27 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 23:18 [PATCH net-next v6 0/5] vsock: SOCK_LINGER rework Michal Luczaj
2025-05-21 23:18 ` [PATCH net-next v6 1/5] vsock/virtio: Linger on unsent data Michal Luczaj
2025-05-21 23:18 ` [PATCH net-next v6 2/5] vsock: Move lingering logic to af_vsock core Michal Luczaj
2025-05-21 23:18 ` [PATCH net-next v6 3/5] vsock/test: Introduce vsock_wait_sent() helper Michal Luczaj
2025-05-22 8:05 ` Stefano Garzarella
2025-05-21 23:18 ` [PATCH net-next v6 4/5] vsock/test: Introduce enable_so_linger() helper Michal Luczaj
2025-05-22 8:05 ` Stefano Garzarella
2025-05-21 23:18 ` [PATCH net-next v6 5/5] vsock/test: Add test for an unexpectedly lingering close() Michal Luczaj
2025-05-22 8:05 ` Stefano Garzarella
2025-05-22 8:08 ` [PATCH net-next v6 0/5] vsock: SOCK_LINGER rework Stefano Garzarella
2025-05-22 22:29 ` Michal Luczaj
2025-05-27 9:50 ` 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=174833943425.1235580.6276796573046054337.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@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).