From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: stefanha@redhat.com, sgarzare@redhat.com, mst@redhat.com,
jasowang@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrii@kernel.org,
mykolal@fb.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] Add support for sockmap to vsock.
Date: Wed, 29 Mar 2023 08:00:25 +0000 [thread overview]
Message-ID: <168007682558.9659.6900016248016625386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230327-vsock-sockmap-v4-0-c62b7cd92a85@bytedance.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 27 Mar 2023 19:11:50 +0000 you wrote:
> We're testing usage of vsock as a way to redirect guest-local UDS
> requests to the host and this patch series greatly improves the
> performance of such a setup.
>
> Compared to copying packets via userspace, this improves throughput by
> 121% in basic testing.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] vsock: support sockmap
https://git.kernel.org/netdev/net-next/c/634f1a7110b4
- [net-next,v4,2/3] selftests/bpf: add vsock to vmtest.sh
https://git.kernel.org/netdev/net-next/c/c7c605c982d6
- [net-next,v4,3/3] selftests/bpf: add a test case for vsock sockmap
https://git.kernel.org/netdev/net-next/c/d61bd8c1fd02
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:[~2023-03-29 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 19:11 [PATCH net-next v4 0/3] Add support for sockmap to vsock Bobby Eshleman
2023-03-27 19:11 ` [PATCH net-next v4 1/3] vsock: support sockmap Bobby Eshleman
2023-03-28 8:20 ` Stefano Garzarella
2023-03-27 19:11 ` [PATCH net-next v4 2/3] selftests/bpf: add vsock to vmtest.sh Bobby Eshleman
2023-03-27 19:11 ` [PATCH net-next v4 3/3] selftests/bpf: add a test case for vsock sockmap Bobby Eshleman
2023-03-29 8:00 ` patchwork-bot+netdevbpf [this message]
2023-04-01 1:06 ` [PATCH net-next v4 0/3] Add support for sockmap to vsock John Fastabend
2023-04-03 11:10 ` 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=168007682558.9659.6900016248016625386.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bobby.eshleman@bytedance.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mst@redhat.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).