Searched refs:workloads (Results 1 – 11 of 11) sorted by relevance
24 for accelerating crypto and compression workloads.35 for accelerating crypto and compression workloads.46 for accelerating crypto and compression workloads.57 for accelerating crypto and compression workloads.68 for accelerating crypto and compression workloads.80 for accelerating crypto and compression workloads.93 Virtual Function for accelerating crypto and compression workloads.105 Virtual Function for accelerating crypto and compression workloads.117 Virtual Function for accelerating crypto and compression workloads.
14 designed to accelerate Deep Learning inference workloads.17 for users to submit workloads to the devices.
18 designed to accelerate Deep Learning inference and training workloads.21 the user to submit workloads to the devices.
33 Some workloads benefit from using it and it generally should be safe45 Some virtualized workloads benefit from using it.
18 for accelerating crypto workloads.
8 for workloads (e.g. DPDK, MPI etc) that uses RDMA verbs to directly
1331 kmem_cache_destroy(s->workloads); in intel_vgpu_clean_submission()1423 s->workloads = kmem_cache_create_usercopy("gvt-g_vgpu_workload", in intel_vgpu_setup_submission()1430 if (!s->workloads) { in intel_vgpu_setup_submission()1539 kmem_cache_free(s->workloads, workload); in intel_vgpu_destroy_workload()1548 workload = kmem_cache_zalloc(s->workloads, GFP_KERNEL); in alloc_workload()1722 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()1736 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()1747 kmem_cache_free(s->workloads, workload); in intel_vgpu_create_workload()
154 struct kmem_cache *workloads; member
191 the CPUs' workloads are. CPU-bound workloads will be more sensitive193 workloads will be less sensitive -- they will not necessarily perform
118 interactive or low latency workloads.
325 adaptability in the face of changing workloads.
Completed in 22 milliseconds