From: Paolo Abeni <pabeni@redhat.com>
To: "Jon Kohler" <jon@nutanix.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Eugenio Pérez" <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 v2] vhost/net: Defer TX queue re-enable until after sendmsg
Date: Thu, 24 Apr 2025 13:48:53 +0200 [thread overview]
Message-ID: <a0894275-6b23-4cff-9e36-a635f776c403@redhat.com> (raw)
In-Reply-To: <20250420010518.2842335-1-jon@nutanix.com>
On 4/20/25 3:05 AM, Jon Kohler wrote:
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index b9b9e9d40951..9b04025eea66 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -769,13 +769,17 @@ static void handle_tx_copy(struct vhost_net *net, struct socket *sock)
> break;
> /* Nothing new? Wait for eventfd to tell us they refilled. */
> if (head == vq->num) {
> + /* If interrupted while doing busy polling, requeue
> + * the handler to be fair handle_rx as well as other
> + * tasks waiting on cpu
> + */
> if (unlikely(busyloop_intr)) {
> vhost_poll_queue(&vq->poll);
> - } else if (unlikely(vhost_enable_notify(&net->dev,
> - vq))) {
> - vhost_disable_notify(&net->dev, vq);
> - continue;
> }
> + /* Kicks are disabled at this point, break loop and
> + * process any remaining batched packets. Queue will
> + * be re-enabled afterwards.
> + */
> break;
> }
It's not clear to me why the zerocopy path does not need a similar change.
> @@ -825,7 +829,14 @@ static void handle_tx_copy(struct vhost_net *net, struct socket *sock)
> ++nvq->done_idx;
> } while (likely(!vhost_exceeds_weight(vq, ++sent_pkts, total_len)));
>
> + /* Kicks are still disabled, dispatch any remaining batched msgs. */
> vhost_tx_batch(net, nvq, sock, &msg);
> +
> + /* All of our work has been completed; however, before leaving the
> + * TX handler, do one last check for work, and requeue handler if
> + * necessary. If there is no work, queue will be reenabled.
> + */
> + vhost_net_busy_poll_try_queue(net, vq);
This will call vhost_poll_queue() regardless of the 'busyloop_intr' flag
value, while AFAICS prior to this patch vhost_poll_queue() is only
performed with busyloop_intr == true. Why don't we need to take care of
such flag here?
@Michael: I assume you prefer that this patch will go through the
net-next tree, right?
Thanks,
Paolo
next prev parent reply other threads:[~2025-04-24 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 1:05 Jon Kohler
2025-04-20 7:32 ` Michael S. Tsirkin
2025-04-20 14:38 ` Jon Kohler
2025-04-24 11:48 ` Paolo Abeni [this message]
2025-04-24 12:11 ` Michael S. Tsirkin
2025-04-24 13:53 ` Jon Kohler
2025-04-24 14:24 ` Michael S. Tsirkin
2025-04-26 19:06 ` Jon Kohler
2025-04-26 19:21 ` Jon Kohler
2025-05-18 21:38 ` Michael S. Tsirkin
2025-05-18 22:21 ` 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=a0894275-6b23-4cff-9e36-a635f776c403@redhat.com \
--to=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®