From: Andra Paraschiv <andraprs@amazon.com> To: netdev <netdev@vger.kernel.org> Cc: linux-kernel <linux-kernel@vger.kernel.org>, "David S . Miller" <davem@davemloft.net>, David Duncan <davdunc@amazon.com>, Dexuan Cui <decui@microsoft.com>, Alexander Graf <graf@amazon.de>, Jorgen Hansen <jhansen@vmware.com>, Jakub Kicinski <kuba@kernel.org>, Stefano Garzarella <sgarzare@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>, Vitaly Kuznetsov <vkuznets@redhat.com>, Andra Paraschiv <andraprs@amazon.com> Subject: [PATCH net-next v2 1/4] vm_sockets: Include flags field in the vsock address data structure Date: Fri, 4 Dec 2020 19:02:32 +0200 [thread overview] Message-ID: <20201204170235.84387-2-andraprs@amazon.com> (raw) In-Reply-To: <20201204170235.84387-1-andraprs@amazon.com> vsock enables communication between virtual machines and the host they are running on. With the multi transport support (guest->host and host->guest), nested VMs can also use vsock channels for communication. In addition to this, by default, all the vsock packets are forwarded to the host, if no host->guest transport is loaded. This behavior can be implicitly used for enabling vsock communication between sibling VMs. Add a flags field in the vsock address data structure that can be used to explicitly mark the vsock connection as being targeted for a certain type of communication. This way, can distinguish between different use cases such as nested VMs and sibling VMs. Use the already available "svm_reserved1" field and mark it as a flags field instead. This field can be set when initializing the vsock address variable used for the connect() call. Changelog v1 -> v2 * Update the field name to "svm_flags". * Split the current patch in 2 patches. Signed-off-by: Andra Paraschiv <andraprs@amazon.com> --- include/uapi/linux/vm_sockets.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/uapi/linux/vm_sockets.h b/include/uapi/linux/vm_sockets.h index fd0ed7221645d..46735376a57a8 100644 --- a/include/uapi/linux/vm_sockets.h +++ b/include/uapi/linux/vm_sockets.h @@ -145,7 +145,7 @@ struct sockaddr_vm { __kernel_sa_family_t svm_family; - unsigned short svm_reserved1; + unsigned short svm_flags; unsigned int svm_port; unsigned int svm_cid; unsigned char svm_zero[sizeof(struct sockaddr) - -- 2.20.1 (Apple Git-117) Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
next prev parent reply other threads:[~2020-12-04 17:03 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-04 17:02 [PATCH net-next v2 0/4] vsock: Add flags field in the vsock address Andra Paraschiv 2020-12-04 17:02 ` Andra Paraschiv [this message] 2020-12-07 9:59 ` [PATCH net-next v2 1/4] vm_sockets: Include flags field in the vsock address data structure Stefano Garzarella 2020-12-07 19:25 ` Paraschiv, Andra-Irina 2020-12-07 21:29 ` Jakub Kicinski 2020-12-08 18:23 ` Paraschiv, Andra-Irina 2020-12-08 18:42 ` Jakub Kicinski 2020-12-09 10:48 ` Stefano Garzarella 2020-12-09 15:17 ` Paraschiv, Andra-Irina 2020-12-09 17:30 ` Jakub Kicinski 2020-12-10 15:29 ` Paraschiv, Andra-Irina 2020-12-04 17:02 ` [PATCH net-next v2 2/4] vm_sockets: Add VMADDR_FLAG_TO_HOST vsock flag Andra Paraschiv 2020-12-07 9:59 ` Stefano Garzarella 2020-12-07 19:45 ` Paraschiv, Andra-Irina 2020-12-04 17:02 ` [PATCH net-next v2 3/4] af_vsock: Set VMADDR_FLAG_TO_HOST flag on the receive path Andra Paraschiv 2020-12-07 9:59 ` Stefano Garzarella 2020-12-04 17:02 ` [PATCH net-next v2 4/4] af_vsock: Assign the vsock transport considering the vsock address flags Andra Paraschiv 2020-12-07 10:00 ` Stefano Garzarella 2020-12-07 19:51 ` Paraschiv, Andra-Irina 2020-12-07 10:05 ` [PATCH net-next v2 0/4] vsock: Add flags field in the vsock address Stefano Garzarella 2020-12-07 19:18 ` Paraschiv, Andra-Irina
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=20201204170235.84387-2-andraprs@amazon.com \ --to=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 \ --subject='Re: [PATCH net-next v2 1/4] vm_sockets: Include flags field in the vsock address data structure' \ /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
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).