From: Julian Anastasov
Date: Wed, 8 Feb 2017 23:05:36 +0200 (EET)
> On Tue, 7 Feb 2017, David Miller wrote:
>
>> > - Now may be old function neigh_output() should be restored
>> > instead of dst_neigh_output?
>>
>> Please elaborate.
>
> As dst_neigh_output does not use the dst arg anymor
Hello,
On Tue, 7 Feb 2017, David Miller wrote:
> From: Julian Anastasov
> Date: Mon, 6 Feb 2017 23:14:10 +0200
>
> > - I failed to understand the CXGB* code, I see dst_confirm()
> > calls but I'm not sure dst_neigh_output() was called. For now
> > I just removed the dst->pending_confi
From: Julian Anastasov
Date: Mon, 6 Feb 2017 23:14:10 +0200
> This patchset addresses the problem of neighbour
> confirmation where received replies from one nexthop
> can cause confirmation of different nexthop when using
> the same dst. Thanks to YueHaibing
> for tracking the dst->pendi
This patchset addresses the problem of neighbour
confirmation where received replies from one nexthop
can cause confirmation of different nexthop when using
the same dst. Thanks to YueHaibing
for tracking the dst->pending_confirm problem.
Sockets can obtain cached output route. Su
