From: patchwork-bot+netdevbpf@kernel.org
To: Jon Kohler <jon@nutanix.com>
Cc: mst@redhat.com, jasowang@redhat.com, eperezma@redhat.com,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] vhost/net: Defer TX queue re-enable until after sendmsg
Date: Tue, 06 May 2025 01:40:35 +0000 [thread overview]
Message-ID: <174649563599.1007977.10317536057166889809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250501020428.1889162-1-jon@nutanix.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Apr 2025 19:04:28 -0700 you wrote:
> In handle_tx_copy, TX batching processes packets below ~PAGE_SIZE and
> batches up to 64 messages before calling sock->sendmsg.
>
> Currently, when there are no more messages on the ring to dequeue,
> handle_tx_copy re-enables kicks on the ring *before* firing off the
> batch sendmsg. However, sock->sendmsg incurs a non-zero delay,
> especially if it needs to wake up a thread (e.g., another vhost worker).
>
> [...]
Here is the summary with links:
- [net-next,v3] vhost/net: Defer TX queue re-enable until after sendmsg
https://git.kernel.org/netdev/net-next/c/8c2e6b26ffe2
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:[~2025-05-06 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 2:04 [PATCH net-next v3] vhost/net: Defer TX queue re-enable until after sendmsg Jon Kohler
2025-05-01 13:44 ` Michael S. Tsirkin
2025-05-06 1:40 ` patchwork-bot+netdevbpf [this message]
2025-09-10 18:58 ` vhost_iotlb_miss tight loop lockup - RE " Jon Kohler
2025-09-10 20:10 ` Michael S. Tsirkin
2025-09-11 5:49 ` Jason Wang
2025-09-11 5:55 ` Michael S. Tsirkin
2025-09-11 13:24 ` Jon Kohler
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=174649563599.1007977.10317536057166889809.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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).