From: Michal Luczaj <mhal@rbox.co>
To: "Stefano Garzarella" <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Michal Luczaj <mhal@rbox.co>
Subject: [PATCH net-next v2 0/3] vsock: SOCK_LINGER rework
Date: Mon, 21 Apr 2025 23:50:40 +0200 [thread overview]
Message-ID: <20250421-vsock-linger-v2-0-fe9febd64668@rbox.co> (raw)
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 v2:
- Comment that some transports do not implement unsent_bytes [Stefano]
- Reduce the indentation of virtio_transport_wait_close() [Stefano]
- Do not linger on shutdown(), expand the commit messages [Paolo]
- Link to v1: https://lore.kernel.org/r/20250407-vsock-linger-v1-0-1458038e3492@rbox.co
Changes in v1:
- Do not assume `unsent_bytes()` is implemented by all transports [Stefano]
- Link to v0: https://lore.kernel.org/netdev/df2d51fd-03e7-477f-8aea-938446f47864@rbox.co/
Signed-off-by: Michal Luczaj <mhal@rbox.co>
---
Michal Luczaj (3):
vsock: Linger on unsent data
vsock: Reduce indentation in virtio_transport_wait_close()
vsock/test: Expand linger test to ensure close() does not misbehave
net/vmw_vsock/virtio_transport_common.c | 29 +++++++++++++++++++----------
tools/testing/vsock/vsock_test.c | 30 +++++++++++++++++++++++++++---
2 files changed, 46 insertions(+), 13 deletions(-)
---
base-commit: 8066e388be48f1ad62b0449dc1d31a25489fa12a
change-id: 20250304-vsock-linger-9026e5f9986c
Best regards,
--
Michal Luczaj <mhal@rbox.co>
next reply other threads:[~2025-04-21 21:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 21:50 Michal Luczaj [this message]
2025-04-21 21:50 ` [PATCH net-next v2 1/3] vsock: Linger on unsent data Michal Luczaj
2025-04-23 15:53 ` Luigi Leonardi
2025-04-23 16:34 ` Stefano Garzarella
2025-04-23 21:06 ` Michal Luczaj
2025-04-24 7:28 ` Stefano Garzarella
2025-04-24 7:52 ` Michal Luczaj
2025-04-24 8:36 ` Stefano Garzarella
2025-04-24 11:24 ` Michal Luczaj
2025-04-28 13:56 ` Stefano Garzarella
2025-04-30 9:13 ` Michal Luczaj
2025-04-21 21:50 ` [PATCH net-next v2 2/3] vsock: Reduce indentation in virtio_transport_wait_close() Michal Luczaj
2025-04-21 21:50 ` [PATCH net-next v2 3/3] vsock/test: Expand linger test to ensure close() does not misbehave Michal Luczaj
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=20250421-vsock-linger-v2-0-fe9febd64668@rbox.co \
--to=mhal@rbox.co \
--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=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
all inboxes | Powered by JetHome®