On Thu, Jan 24, 2019 at 12:30:08PM -0200, Flavio Leitner wrote:
> On Wed, Jan 23, 2019 at 12:13:25PM -0800, Ben Pfaff wrote:
> > I'm not so happy about reverting without having the followup ready. How
> > close are we to having the followup? Basically we've got two problems
> > here. Without the
On Wed, Jan 23, 2019 at 12:13:25PM -0800, Ben Pfaff wrote:
> I'm not so happy about reverting without having the followup ready. How
> close are we to having the followup? Basically we've got two problems
> here. Without the revert, we have one of them; with the revert, we have
> the other one.
I'm not so happy about reverting without having the followup ready. How
close are we to having the followup? Basically we've got two problems
here. Without the revert, we have one of them; with the revert, we have
the other one. I'd rather not trade one for the other, that's not
ideal. It woul
Hi,
Just a reminder about this revert.
On Thu, Dec 13, 2018 at 12:30:47PM -0200, Flavio Leitner wrote:
>
> This should be applied to branch-2.10 as well.
And now branch-2.11
Thanks,
fbl
>
> (BTW, I had CC few folks in the patchset, but I am only seeing Guru, so
> I am adding them to this
This should be applied to branch-2.10 as well.
(BTW, I had CC few folks in the patchset, but I am only seeing Guru, so
I am adding them to this email just in case)
Thanks,
fbl
On Thu, Dec 13, 2018 at 12:24:45PM -0200, Flavio Leitner wrote:
> The optimization introduced a regression in OSP env
The optimization introduced a regression in OSP environments using
internal ports in other netns. Their networking configuration is lost
when the service is restarted because the ports are recreated now.
Before the patch it checked using netlink if the port with a specific
"name" was already there
