[Dynamic Buffer Calc] Support dynamic buffer calculation on top of po…

…rt auto negotiation (sonic-net#1762)

- What I did
Update the speed used for headroom calculating according to port auto-negotiation change.
The speed taken into the calculation is now called effective speed in the code.

- Why I did it
One logic was to take the configured speed into account when calculating the headroom because it's the maximum possible speed at which a port runs.
As port auto-negotiation supported, this logic needs to be updated accordingly:
The maximum possible speed is no longer the configured one with auto-negotiation enabled.
So the speed taken into account should be:

If port auto-negotiation is enabled:
maximum speed in adv_speeds if it is configured
maximum speed in supported_speeds otherwise
Otherwise: the configured speed

- How I verified it
Run regression test and vs test.

Signed-off-by: Stephen Sun stephens@nvidia.com

cfgmgr/buffermgrd.cpp

@@ -180,7 +180,8 @@ int main(int argc, char **argv)
                 TableConnector(&cfgDb, CFG_BUFFER_PORT_INGRESS_PROFILE_LIST_NAME),
                 TableConnector(&cfgDb, CFG_BUFFER_PORT_EGRESS_PROFILE_LIST_NAME),
                 TableConnector(&cfgDb, CFG_DEFAULT_LOSSLESS_BUFFER_PARAMETER),
-                TableConnector(&stateDb, STATE_BUFFER_MAXIMUM_VALUE_TABLE)
+                TableConnector(&stateDb, STATE_BUFFER_MAXIMUM_VALUE_TABLE),
+                TableConnector(&stateDb, STATE_PORT_TABLE_NAME)
             };
             cfgOrchList.emplace_back(new BufferMgrDynamic(&cfgDb, &stateDb, &applDb, buffer_table_connectors, db_items_ptr));
         }