From 88550585b3ec252f6a8f755b130782fd94631a6f Mon Sep 17 00:00:00 2001 From: Gris Ge Date: Thu, 21 Mar 2024 20:57:46 +0800 Subject: [PATCH] YAML API: Add `cwnd` property of route Signed-off-by: Gris Ge --- devel/yaml_api.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/devel/yaml_api.md b/devel/yaml_api.md index e0be906..15c152b 100644 --- a/devel/yaml_api.md +++ b/devel/yaml_api.md @@ -1520,6 +1520,13 @@ Each route entry could have these parameters: route, it will only delete routes __without__ `next-hop-address`. * `metric`: Integer. Set to -1 for let backend decide. * `table-id`: Integer. Set to 0 for main table id 254. + * `cwnd`: Integer. TCP congestion window. According to linux kernel, The + `cwnd` property of route requires the `lock cwnd` flag been set at the same + time, otherwise the `cwnd` will take effect. Hence, on querying, nmstate + treat routes without `lock cwnd` flag as empty `cwnd`. When applying, + nmstate backend always set `lock cwnd`. If you want to modify existing + `cwnd`, like modifying other route properties, you need to mark old + route as `state: absnet` and append new route. ## Route Rules