Zachary f2d449d486 burst should be set near max-rate ... Burst value for TCP traffic should be set as 80% of desired bandwidth limit value. For example, if the bandwidth limit is set to 1000kbps then enough burst value will be 800kbit. If the configured burst value is too low, achieved bandwidth limit will be lower than expected. If the configured burst value is too high, too few packets could be limited and achieved bandwidth limit would be higher than expected. So we should recommend a correct example in case that user ignores the note. Change-Id: Iefea3ce699c39e217e89dec93a8fe8ea1a90ac82		2017-12-05 09:28:30 +08:00
..
_static	Neutron Feature Classification	2017-03-15 23:31:58 +00:00
admin	burst should be set near max-rate	2017-12-05 09:28:30 +08:00
cli	import content from cli-reference in openstack-manuals	2017-07-10 18:06:29 +00:00
configuration	Add auto-generated config reference	2017-07-30 21:14:40 +00:00
contributor	Merge "ovsfw: Use multiple priorities in RULES_*_TABLE"	2017-11-24 06:16:24 +00:00
ext	Add project links to feature classification matrix	2017-07-25 16:28:59 -07:00
feature_classification	update static urls for pike	2017-09-01 12:37:13 -06:00
install	clarify nova prereq for controller install docs	2017-11-27 08:55:14 -07:00
conf.py	add doc link validation to release checklist and tox	2017-09-21 15:24:03 -06:00
index.rst	Replace http with https for doc links	2017-11-01 22:10:51 +00:00