ba641f2076
The setup and configuration of the PMD is not performance sensitive, but is not thread safe either. It is possible that the multiple read/writes during PMD setup and configuration could be corrupted in a multi-thread environment. Since this is not performance sensitive, the developer can choose to add their own layer to provide thread-safe setup and configuration. It is expected that, in most applications, the initial configuration of the network ports would be done by a single thread at startup. In the case of exception on the event queue, the event queue and corresponding Rx/Tx queue should be restarted in the Rx/Tx queue polling context. These operations require access to the device control which should be serialized. The device level lock will do the job. Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Andy Moreton <amoreton@solarflare.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> |
||
|---|---|---|
| .. | ||
| base | ||
| efsys.h | ||
| Makefile | ||
| rte_pmd_sfc_efx_version.map | ||
| sfc_debug.h | ||
| sfc_ethdev.c | ||
| sfc_kvargs.c | ||
| sfc_kvargs.h | ||
| sfc_log.h | ||
| sfc_mcdi.c | ||
| sfc.c | ||
| sfc.h | ||