On Mon, Dec 21, 2009 at 12:47 PM, Martin Casado <cas...@nicira.com> wrote: > I agree that if the problem is timeout due to loss from overload, then the > only solution is prioritization.
In general yes, but the current discovery algorithm is fairly brittle. With a large number of ports (48) on a hardware switch, even a small amount of packet loss it can falsely report down links. Part of the goal of the rewrite is to address this issue. > Question for the slicing folks, does slicing extend to the control channel > (packets set to the controller?) In addition to what Yiannis said (short story == "not yet"), Jean from HP developed a "rate limiter" openflow action as a vendor extension that can affect control and data traffic, so that could be used here. I think this is a useful primitive and something I'm hoping will making it into a future release of openflow (1.1?). - Rob . _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
