Searched refs:yield (Results 1 – 6 of 6) sorted by relevance
71 char yield[256]; /**< PCI sub-device arguments. */ member328 char in[RTE_MAX(sizeof(ctx->yield), 256u)]; in vdev_netvsc_sysfs_readlink()373 char buf[RTE_MAX(sizeof(ctx->yield), 256u)]; in vdev_netvsc_device_probe()409 if (strcmp(addr, ctx->yield)) in vdev_netvsc_device_probe()436 memcpy(ctx->yield, addr, len + 1); in vdev_netvsc_device_probe()580 ctx->yield[0] = '\0'; in vdev_netvsc_netvsc_probe()
12 movement during the traffic split. This can yield better performance with
259 ``spec`` and ``last``, which may yield unexpected results if not used4357 yield a large number of hidden flow rules. It is thus suggested to only
981 subtracted from the address of the dummy header to yield the address of the
426 packet priority in order to yield the enqueue/drop decision for a specific packet
3876 These yield identical results::