From: Bobby Eshleman <bobbyeshleman@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Bobby Eshleman <bobby.eshleman@bytedance.com>,
Cong Wang <cong.wang@bytedance.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org,
Arseniy Krasnov <AVKrasnov@sberdevices.ru>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Eric Dumazet <edumazet@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v10] virtio/vsock: replace virtio_vsock_pkt with sk_buff
Date: Tue, 17 Jan 2023 23:14:44 +0000 [thread overview]
Message-ID: <Y8cr5KosN5kZaOgK@bullseye> (raw)
In-Reply-To: <20230116111207.yxlwh4jlejtn4ple@sgarzare-redhat>
On Mon, Jan 16, 2023 at 12:12:07PM +0100, Stefano Garzarella wrote:
> On Fri, Jan 13, 2023 at 10:21:37PM +0000, Bobby Eshleman wrote:
> > This commit changes virtio/vsock to use sk_buff instead of
> > virtio_vsock_pkt. Beyond better conforming to other net code, using
> > sk_buff allows vsock to use sk_buff-dependent features in the future
> > (such as sockmap) and improves throughput.
> >
> > This patch introduces the following performance changes:
> >
> > Tool: Uperf
> > Env: Phys Host + L1 Guest
> > Payload: 64k
> > Threads: 16
> > Test Runs: 10
> > Type: SOCK_STREAM
> > Before: commit b7bfaa761d760 ("Linux 6.2-rc3")
> >
> > Before
> > ------
> > g2h: 16.77Gb/s
> > h2g: 10.56Gb/s
> >
> > After
> > -----
> > g2h: 21.04Gb/s
> > h2g: 10.76Gb/s
> >
> > Signed-off-by: Bobby Eshleman <bobby.eshleman@bytedance.com>
> >
> > ---
> > Changes in v10:
> > - vhost/vsock: use virtio_vsock_skb_dequeue()
> > - vhost/vsock: remove extra iov_length() call
> > - vhost/vsock: also consider hdr when evaluating that incoming size is
> > valid
> > - new uperf data
>
> Tests seem fine!
>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Thank you for all of the reviews and testing!
Best,
Bobby
next prev parent reply other threads:[~2023-01-18 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 22:21 [PATCH net-next v10] virtio/vsock: replace virtio_vsock_pkt with sk_buff Bobby Eshleman
2023-01-16 11:12 ` Stefano Garzarella
2023-01-17 23:14 ` Bobby Eshleman [this message]
2023-01-16 13:30 ` patchwork-bot+netdevbpf
2023-01-18 6:20 ` Michael S. Tsirkin
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=Y8cr5KosN5kZaOgK@bullseye \
--to=bobbyeshleman@gmail.com \
--cc=AVKrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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-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