On Sun, Jan 7, 2018 at 1:46 AM, Song Liu wrote:
>
>> On Jan 5, 2018, at 12:09 AM, Yafang Shao wrote:
>>
>> On Fri, Jan 5, 2018 at 3:21 PM, Song Liu wrote:
>>>
On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote:
sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments.
>>
> On Jan 5, 2018, at 12:09 AM, Yafang Shao wrote:
>
> On Fri, Jan 5, 2018 at 3:21 PM, Song Liu wrote:
>>
>>> On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote:
>>>
>>> sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments.
>>> Then we can conveniently use these two arguments to
On Fri, Jan 5, 2018 at 3:21 PM, Song Liu wrote:
>
>> On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote:
>>
>> sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments.
>> Then we can conveniently use these two arguments to do the filter.
>>
>> Suggested-by: Brendan Gregg
>> Signed-off-
> On Jan 4, 2018, at 10:42 PM, Yafang Shao wrote:
>
> sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments.
> Then we can conveniently use these two arguments to do the filter.
>
> Suggested-by: Brendan Gregg
> Signed-off-by: Yafang Shao
> ---
> include/trace/events/sock.h |
sk->sk_protocol and sk->sk_family are exposed as tracepoint arguments.
Then we can conveniently use these two arguments to do the filter.
Suggested-by: Brendan Gregg
Signed-off-by: Yafang Shao
---
include/trace/events/sock.h | 24 ++--
net/ipv4/af_inet.c | 6 --
