[dpdk-dev] SIMD Rx/Tx paths

Thomas Monjalon thomas at monjalon.net
Mon May 15 14:35:55 CEST 2017


Hi,

I would like to open a discussion about SIMD code in drivers.

I think we should not have different behaviours or features capabilities,
in the different code paths of a same driver.
I suggest to consider such differences as exceptions.
So we should merge features files (i.e. matrix columns),
and remove these files:

% ls doc/guides/nics/features/*_vec.ini

doc/guides/nics/features/fm10k_vec.ini
doc/guides/nics/features/fm10k_vf_vec.ini
doc/guides/nics/features/i40e_vec.ini
doc/guides/nics/features/i40e_vf_vec.ini
doc/guides/nics/features/ixgbe_vec.ini
doc/guides/nics/features/ixgbe_vf_vec.ini
doc/guides/nics/features/virtio_vec.ini

If a feature is not supported in all code paths of a driver,
it must be marked as partially (P) supported.

Then the mid-term goal will be to try removing these inconsistencies.

Opinions/comments?


More information about the dev mailing list