RE: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-20 Thread Dexuan Cui
> -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 > >> > >> > +

RE: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-20 Thread Dexuan Cui
-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);

Re: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-17 Thread Vitaly Kuznetsov
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"); >> >> Debug logging just to state that a function is called is not appropriate, >> we have very

Re: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-17 Thread Vitaly Kuznetsov
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

RE: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-16 Thread Dexuan Cui
> 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

RE: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-16 Thread Dexuan Cui
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

Re: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-15 Thread David Miller
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 kernel that can do that transparently, and more. PLease remove

Re: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature

2015-07-15 Thread David Miller
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