Daniel Borkmann writes:
> On 11/22/2016 06:23 AM, Cong Wang wrote:
>> On Thu, Nov 17, 2016 at 1:02 PM, Cong Wang wrote:
>>> On Wed, Nov 16, 2016 at 2:16 PM, Roman Mashak wrote:
Userland client should be able to read an event, and reflect it back to
the kernel, therefore it needs to ex
On 11/22/2016 06:23 AM, Cong Wang wrote:
On Thu, Nov 17, 2016 at 1:02 PM, Cong Wang wrote:
On Wed, Nov 16, 2016 at 2:16 PM, Roman Mashak wrote:
Userland client should be able to read an event, and reflect it back to
the kernel, therefore it needs to extract complete set of netlink flags.
For
On Thu, Nov 17, 2016 at 1:02 PM, Cong Wang wrote:
> On Wed, Nov 16, 2016 at 2:16 PM, Roman Mashak wrote:
>> Userland client should be able to read an event, and reflect it back to
>> the kernel, therefore it needs to extract complete set of netlink flags.
>>
>> For example, this will allow "tc mo
On Wed, Nov 16, 2016 at 2:16 PM, Roman Mashak wrote:
> Userland client should be able to read an event, and reflect it back to
> the kernel, therefore it needs to extract complete set of netlink flags.
>
> For example, this will allow "tc monitor" to distinguish Add and Replace
> operations.
>
> S
From: Roman Mashak
Date: Wed, 16 Nov 2016 17:16:10 -0500
> Userland client should be able to read an event, and reflect it back to
> the kernel, therefore it needs to extract complete set of netlink flags.
>
> For example, this will allow "tc monitor" to distinguish Add and Replace
> operations.
Userland client should be able to read an event, and reflect it back to
the kernel, therefore it needs to extract complete set of netlink flags.
For example, this will allow "tc monitor" to distinguish Add and Replace
operations.
Signed-off-by: Roman Mashak
Signed-off-by: Jamal Hadi Salim
---
