On Thu, 2016-10-13 at 09:54 -0400, David Miller wrote:
> Applied, thanks Eric.
>
> Want me to queue this up for -stable too?
No thanks, it just occurred to me during a debugging session.
From: Eric Dumazet
Date: Sun, 09 Oct 2016 20:25:55 -0700
> From: Eric Dumazet
>
> There are two ways to get tc filters from kernel to user space.
>
> 1) Full dump (tc_dump_tfilter())
> 2) RTM_GETTFILTER to get one precise filter, reducing overhead.
On 16-10-13 03:46 AM, Eric Dumazet wrote:
On Wed, 2016-10-12 at 09:36 -0700, Cong Wang wrote:
On Sun, Oct 9, 2016 at 8:25 PM, Eric Dumazet wrote:
+ if (unicast)
+ return netlink_unicast(net->rtnl, skb, portid, MSG_DONTWAIT);
Nit: rtnl_unicast() is
On Wed, 2016-10-12 at 09:36 -0700, Cong Wang wrote:
> On Sun, Oct 9, 2016 at 8:25 PM, Eric Dumazet wrote:
> > + if (unicast)
> > + return netlink_unicast(net->rtnl, skb, portid,
> > MSG_DONTWAIT);
>
> Nit: rtnl_unicast() is simpler.
I copied code in
On Sun, Oct 9, 2016 at 8:25 PM, Eric Dumazet wrote:
> + if (unicast)
> + return netlink_unicast(net->rtnl, skb, portid, MSG_DONTWAIT);
Nit: rtnl_unicast() is simpler.
On 16-10-09 11:25 PM, Eric Dumazet wrote:
From: Eric Dumazet
There are two ways to get tc filters from kernel to user space.
1) Full dump (tc_dump_tfilter())
2) RTM_GETTFILTER to get one precise filter, reducing overhead.
The second operation is unfortunately
From: Eric Dumazet
There are two ways to get tc filters from kernel to user space.
1) Full dump (tc_dump_tfilter())
2) RTM_GETTFILTER to get one precise filter, reducing overhead.
The second operation is unfortunately broadcasting its result,
polluting "tc monitor" users.