Bogo-flow-ops

[billsnow]

Status: Open Project: Flowvisor Component/s: Core Affects Version/s: 0.7.2 Fix Version/s: Long Term

Type: New Feature Priority: Trivial Reporter: Nick Bastin Assignee: Rob Sherwood Resolution: Unresolved Votes: 0 Labels: None Remaining Estimate: Not Specified Time Spent: Not Specified Original Estimate: Not Specified

Description
An implementation independent benchmark for deciding how many openflow messages (by type) a guest should be able to send without violating isolation See the Bogo-Flow-Ops page on the CleanSlate wiki

Comments
Comment by Rob Sherwood [ 04/Jul/11 ] The general idea here is that each switch has a hardware limit in terms of the number of messages it can handle per second (generally, very message, firmware, and hardware specific). This feature request proposes doing a benchmark on each switch to figure out what those limits are, and using the limits to infer how much per-slice-per-message rate limiting to do.

Original issue: https://openflow.stanford.edu/bugs/browse/FLOWVISOR-5