From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: davem@davemloft.net, Gerard Garcia <ggarcia@abra.uab.cat>,
kvm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net] vsock/virtio: postpone packet delivery to monitoring devices
Date: Tue, 21 Apr 2020 16:42:46 +0100 [thread overview]
Message-ID: <20200421154246.GA47385@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200421092527.41651-1-sgarzare@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Tue, Apr 21, 2020 at 11:25:27AM +0200, Stefano Garzarella wrote:
> We delivering packets to monitoring devices, before to check if
> the virtqueue has enough space.
"We [are] delivering packets" and "before to check" -> "before
checking". Perhaps it can be rewritten as:
Packets are delivered to monitoring devices before checking if the
virtqueue has enough space.
>
> If the virtqueue is full, the transmitting packet is queued up
> and it will be sent in the next iteration. This causes the same
> packet to be delivered multiple times to monitoring devices.
>
> This patch fixes this issue, postponing the packet delivery
> to monitoring devices, only when it is properly queued in the
s/,//
> virqueue.
s/virqueue/virtqueue/
> @@ -137,6 +135,11 @@ virtio_transport_send_pkt_work(struct work_struct *work)
> break;
> }
>
> + /* Deliver to monitoring devices all correctly transmitted
> + * packets.
> + */
> + virtio_transport_deliver_tap_pkt(pkt);
> +
The device may see the tx packet and therefore receive a reply to it
before we can call virtio_transport_deliver_tap_pkt(). Does this mean
that replies can now appear in the packet capture before the transmitted
packet?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-21 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:25 [PATCH net] vsock/virtio: postpone packet delivery to monitoring devices Stefano Garzarella
2020-04-21 15:42 ` Stefan Hajnoczi [this message]
2020-04-21 16:17 ` Stefano Garzarella
2020-04-22 16:54 ` Stefan Hajnoczi
2020-04-24 10:35 ` Stefano Garzarella
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=20200421154246.GA47385@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=davem@davemloft.net \
--cc=ggarcia@abra.uab.cat \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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