Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1451147
| From | Dexuan Cui <decui@microsoft.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets |
| Date | 2016-07-27 11:30 +0200 |
| Message-ID | <rZtk6-5Wg-19@gated-at.bofh.it> (permalink) |
| References | <rZ2jU-5SK-15@gated-at.bofh.it> <rZ36h-6p2-5@gated-at.bofh.it> <rZ4F3-7pO-23@gated-at.bofh.it> <rZeEp-52r-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
> From: David Miller [mailto:davem@davemloft.net] > Sent: Wednesday, July 27, 2016 1:45 > To: Dexuan Cui <decui@microsoft.com> > > From: Dexuan Cui <decui@microsoft.com> > Date: Tue, 26 Jul 2016 07:09:41 +0000 > > > I googled "S390 hypervisor socket" but didn't find anything related (I think). > > That would be net/iucv/ Thanks for the info! I'll look into this. > There's also VMWare's stuff under net/vmw_vsock > > It's just absolutely rediculous to make a new hypervisor socket > interface over and over again, so much code duplication and > replication. I agree on this principle of avoiding duplication. However my feeling is: IMHO different hypervisor sockets were developed independently without coordination and the implementation details could be so different that an enough generic framework/infrastructure is difficult, e.g., at first glance, it looks AF_IUCV is quite different from AF_VSOCK and this might explain why AF_VSOCK wasn't built on AF_IUCV(?). I'll dig more into AF_IUCV, AF_VSOCK and AF_HYPERV and figure out what is the best direction I should go. Thanks, -- Dexuan
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets David Miller <davem@davemloft.net> - 2016-07-26 02:40 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-26 05:10 +0200
Re: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets David Miller <davem@davemloft.net> - 2016-07-26 06:40 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-26 07:30 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-26 09:10 +0200
Re: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Michal Kubecek <mkubecek@suse.cz> - 2016-07-26 12:00 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-26 15:30 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-27 11:30 +0200
Re: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets David Miller <davem@davemloft.net> - 2016-07-26 19:50 +0200
RE: [PATCH v18 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui <decui@microsoft.com> - 2016-07-27 11:30 +0200
csiph-web