Searched refs:tx_pp (Results 1 – 8 of 8) sorted by relevance
821 int tx_pp = sh->config.tx_pp; in mlx5_txpp_create() local825 sh->txpp.tick = tx_pp >= 0 ? tx_pp : -tx_pp; in mlx5_txpp_create()826 sh->txpp.test = !!(tx_pp < 0); in mlx5_txpp_create()894 if (!sh->config.tx_pp) { in mlx5_txpp_start()904 if (sh->config.tx_pp > 0) { in mlx5_txpp_start()
1192 config->tx_pp = tmp; in mlx5_dev_args_check_handler()1315 if (config->tx_pp && !sh->dev_cap.txpp_en) { in mlx5_shared_dev_ctx_args_config()1320 if (!config->tx_pp && config->tx_skew) { in mlx5_shared_dev_ctx_args_config()1335 DRV_LOG(DEBUG, "\"tx_pp\" is %d.", config->tx_pp); in mlx5_shared_dev_ctx_args_config()2584 if (sh->config.tx_pp ^ config->tx_pp) { in mlx5_probe_again_args_validate()
112 if (priv->sh->config.tx_pp || in mlx5_get_tx_port_offloads()
1354 txq_data->wait_on_time = !!(!sh->config.tx_pp && in mlx5_txq_devx_obj_new()
297 int tx_pp; /* Timestamp scheduling granularity in nanoseconds. */ member
311 - To provide the packet send scheduling on mbuf timestamps the ``tx_pp``324 can be estimated as ``tx_pp`` option (in nanoseconds) multiplied by 2^23.853 - ``tx_pp`` parameter [int]861 By default (if the ``tx_pp`` is not specified) send scheduling on timestamps867 is advertised and handled regardless ``tx_pp`` parameter presence.874 should be provided in nanoseconds and is valid only if ``tx_pp`` parameter is
1038 txq_data->wait_on_time = !!(!priv->sh->config.tx_pp && in mlx5_txq_ibv_obj_new()
1524 if (sh->config.tx_pp && in mlx5_dev_spawn()