-Original Message-
From: Vitaly Kuznetsov
Sent: Friday, July 17, 2015 23:04
To: Dexuan Cui
Dexuan Cui writes:
From: David Miller
Sent: Thursday, July 16, 2015 12:19
From: Dexuan Cui
Date: Tue, 14 Jul 2015 03:00:48 -0700
+pr_debug(hvsock_sk_destruct: called\n);
Dexuan Cui de...@microsoft.com writes:
From: David Miller
Sent: Thursday, July 16, 2015 12:19
From: Dexuan Cui
Date: Tue, 14 Jul 2015 03:00:48 -0700
+ pr_debug(hvsock_sk_destruct: called\n);
Debug logging just to state that a function is called is not appropriate,
we have very
From: David Miller
Sent: Thursday, July 16, 2015 12:19
From: Dexuan Cui
Date: Tue, 14 Jul 2015 03:00:48 -0700
+ pr_debug(hvsock_sk_destruct: called\n);
Debug logging just to state that a function is called is not appropriate,
we have very sophisticated tracing facilities in the
From: Dexuan Cui de...@microsoft.com
Date: Tue, 14 Jul 2015 03:00:48 -0700
+ pr_debug(hvsock_sk_destruct: called\n);
Debug logging just to state that a function is called is not appropriate,
we have very sophisticated tracing facilities in the kernel that can do
that transparently, and
Hyper-V VM sockets (hvsock) supplies a byte-stream based communication
mechanism between the host and a guest. It's kind of TCP over VMBus, but
the transportation layer (VMBus) is much simpler than IP. With Hyper-V VM
Sockets, applications between the host and a guest can talk with each
other
