Searched hist:c1d8e3fb (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/drivers/net/ethernet/microchip/vcap/ |
H A D | vcap_api.h | c1d8e3fb Mon Nov 28 08:29:59 CST 2022 Horatiu Vultur <horatiu.vultur@microchip.com> net: microchip: vcap: Change how the rule id is generated
Currently whenever a new rule id is generated, it picks up the next number bigger than previous id. So it would always be 1, 2, 3, etc. When the rule with id 1 will be deleted and a new rule will be added, it will have the id 4 and not id 1. In theory this can be a problem if at some point a rule will be added and removed ~0 times. Then no more rules can be added because there are no more ids.
Change this such that when a new rule is added, search for an empty rule id starting with value of 1 as value 0 is reserved.
Fixes: c9da1ac1c212 ("net: microchip: sparx5: Adding initial tc flower support for VCAP API") Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com> Link: https://lore.kernel.org/r/20221128142959.8325-1-horatiu.vultur@microchip.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
|
H A D | vcap_api.c | c1d8e3fb Mon Nov 28 08:29:59 CST 2022 Horatiu Vultur <horatiu.vultur@microchip.com> net: microchip: vcap: Change how the rule id is generated
Currently whenever a new rule id is generated, it picks up the next number bigger than previous id. So it would always be 1, 2, 3, etc. When the rule with id 1 will be deleted and a new rule will be added, it will have the id 4 and not id 1. In theory this can be a problem if at some point a rule will be added and removed ~0 times. Then no more rules can be added because there are no more ids.
Change this such that when a new rule is added, search for an empty rule id starting with value of 1 as value 0 is reserved.
Fixes: c9da1ac1c212 ("net: microchip: sparx5: Adding initial tc flower support for VCAP API") Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com> Link: https://lore.kernel.org/r/20221128142959.8325-1-horatiu.vultur@microchip.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
|