On Fri, 7 Feb 2025 12:43:00 +0000
Soumyadeep Hore <soumyadeep.h...@intel.com> wrote:
> diff --git a/drivers/net/intel/common/tx.h b/drivers/net/intel/common/tx.h
> index d9cf4474fc..f3777fa9e7 100644
> --- a/drivers/net/intel/common/tx.h
> +++ b/drivers/net/intel/common/tx.h
> @@ -35,6 +35,7 @@ struct ci_tx_queue {
> volatile struct i40e_tx_desc *i40e_tx_ring;
> volatile struct iavf_tx_desc *iavf_tx_ring;
> volatile struct ice_tx_desc *ice_tx_ring;
> + volatile struct ice_ts_desc *ice_tstamp_ring;
> volatile union ixgbe_adv_tx_desc *ixgbe_tx_ring;
> };
> volatile uint8_t *qtx_tail; /* register address of tail */
> @@ -76,6 +77,10 @@ struct ci_tx_queue {
Why so heavy use of volatile here? Volatile generates worst case code is there
something
odd about the hardware or driver?
