From: patchwork-bot+netdevbpf@kernel.org
To: Paraschiv@ci.codeaurora.org, Andra-Irina <andraprs@amazon.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, davdunc@amazon.com, decui@microsoft.com,
graf@amazon.de, jhansen@vmware.com, kuba@kernel.org,
sgarzare@redhat.com, stefanha@redhat.com, vkuznets@redhat.com
Subject: Re: [PATCH net-next v4 0/5] vsock: Add flags field in the vsock address
Date: Tue, 15 Dec 2020 03:40:08 +0000 [thread overview]
Message-ID: <160800360863.3580.11859617867656861413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201214161122.37717-1-andraprs@amazon.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 14 Dec 2020 18:11:17 +0200 you wrote:
> vsock enables communication between virtual machines and the host they are
> running on. Nested VMs can be setup to use vsock channels, as the multi
> transport support has been available in the mainline since the v5.5 Linux kernel
> has been released.
>
> Implicitly, if no host->guest vsock transport is loaded, all the vsock packets
> are forwarded to the host. This behavior can be used to setup communication
> channels between sibling VMs that are running on the same host. One example can
> be the vsock channels that can be established within AWS Nitro Enclaves
> (see Documentation/virt/ne_overview.rst).
>
> [...]
Here is the summary with links:
- [net-next,v4,1/5] vm_sockets: Add flags field in the vsock address data structure
https://git.kernel.org/netdev/net-next/c/dc8eeef73b63
- [net-next,v4,2/5] vm_sockets: Add VMADDR_FLAG_TO_HOST vsock flag
https://git.kernel.org/netdev/net-next/c/caaf95e0f23f
- [net-next,v4,3/5] vsock_addr: Check for supported flag values
https://git.kernel.org/netdev/net-next/c/cada7ccd9dc7
- [net-next,v4,4/5] af_vsock: Set VMADDR_FLAG_TO_HOST flag on the receive path
https://git.kernel.org/netdev/net-next/c/1b5f2ab98e7f
- [net-next,v4,5/5] af_vsock: Assign the vsock transport considering the vsock address flags
https://git.kernel.org/netdev/net-next/c/7f816984f439
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-15 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 16:11 [PATCH net-next v4 0/5] vsock: Add flags field in the vsock address Andra Paraschiv
2020-12-14 16:11 ` [PATCH net-next v4 1/5] vm_sockets: Add flags field in the vsock address data structure Andra Paraschiv
2020-12-14 16:11 ` [PATCH net-next v4 2/5] vm_sockets: Add VMADDR_FLAG_TO_HOST vsock flag Andra Paraschiv
2020-12-14 16:11 ` [PATCH net-next v4 3/5] vsock_addr: Check for supported flag values Andra Paraschiv
2020-12-14 17:07 ` Stefano Garzarella
2020-12-14 16:11 ` [PATCH net-next v4 4/5] af_vsock: Set VMADDR_FLAG_TO_HOST flag on the receive path Andra Paraschiv
2020-12-14 16:11 ` [PATCH net-next v4 5/5] af_vsock: Assign the vsock transport considering the vsock address flags Andra Paraschiv
2020-12-14 17:09 ` [PATCH net-next v4 0/5] vsock: Add flags field in the vsock address Stefano Garzarella
2020-12-14 18:19 ` Paraschiv, Andra-Irina
2020-12-15 3:40 ` patchwork-bot+netdevbpf [this message]
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=160800360863.3580.11859617867656861413.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Paraschiv@ci.codeaurora.org \
--cc=andraprs@amazon.com \
--cc=davdunc@amazon.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=graf@amazon.de \
--cc=jhansen@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=vkuznets@redhat.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).