Hello, Thanks for the very fast replies.
I do understand the queues are per-port, sorry. I was thinking about huge networks with dozens of slices, which one isolated from the other. And to this end i was planning to use the queuing system, but this limit of 8 queues would limit me to 8 slices, i guess. So does OpenVSwitch (software switches) don't have this limitation? So they can use any way they want to classify packets into queues? Peace! Victor T. On 26 April 2011 01:22, Dan Talayco <[email protected]> wrote: > Hi Victor-- > > First, note that queues are per-port. Second, can you be more specific about > what you're referring to for this limit? Is there a particular implementation > you're looking at? Many implementations use 8 queues as the queuing is > associated with the 3 priority bits in the VLAN tag (for example). I don't > believe there's an explicit limitation in the spec which requires that queues > be defined and configured externally, and only an opaque "queue ID" be used > to identify the queue for the enqueue action and stats-get operation within > the protocol. > > -Dan > > On Monday, April 25, 2011 at 8:43 PM, Victor Torres wrote: >> Hello, >> >> As i was studying the queue mechanisms of OpenFlow 1.0, i found out >> that there can be a Max of 8 queues on a single switch, is that true? >> Are there any workarounds for this? >> Anyone knows if OpenVSwitch has the same limitation (don't know if it >> is a protocol issue, or implementation issue)? >> >> >> Thanks in advance, >> >> Peace! >> Victor T. >> _______________________________________________ >> openflow-discuss mailing list >> [email protected] >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> > > _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
