Searched refs:policies (Results 1 – 12 of 12) sorted by relevance
| /dpdk/examples/vm_power_manager/ |
| H A D | channel_monitor.c | 479 policies[i].pkt = *pkt; in update_policy() 480 get_pcpu_to_control(&policies[i]); in update_policy() 484 if (get_pfid(&policies[i]) < 0) { in update_policy() 490 policies[i].enabled = 1; in update_policy() 496 if (policies[i].enabled == 0) { in update_policy() 497 policies[i].pkt = *pkt; in update_policy() 498 get_pcpu_to_control(&policies[i]); in update_policy() 508 policies[i].enabled = 1; in update_policy() 527 policies[i].enabled = 0; in remove_policy() 1154 if (policies[j].enabled == 1) in run_channel_monitor() [all …]
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | traffic_metering_and_policing.rst | 60 * There is a meter policy API to manage pre-defined policies for meter. 87 #. The application creates the required meter policies by using the
|
| H A D | link_bonding_poll_mode_drv_lib.rst | 78 transmission policies supported are layer 2+3, this takes the IP source and 307 There are 3 supported transmission policies for bonded device running in 326 All these policies support 802.1Q VLAN Ethernet packets, as well as IPv4, IPv6 443 to l2 (layer 2) forwarding, the other transmission policies available are
|
| H A D | poll_mode_drv.rst | 76 …nversely, NIC PMD functions should not impede the benefits expected by upper-level global policies, 77 or worse prevent such policies from being applied. 81 to dynamically adapt its overall behavior through different global loop policies, such as:
|
| H A D | env_abstraction_layer.rst | 776 …5. It MUST not be used by multi-producer/consumer pthreads, whose scheduling policies are SCHED_FI…
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | vm_power_management.rst | 34 - **The acceptance of power management policies from VM applications.** 53 directs frequency changes and policies to the host monitor rather than 139 and policies in JSON format. The JSON interfaces provide a more 141 of requests and policies. See :ref:`power_man_requests` for more information. 608 ``virtio-serial`` interface for VM power policies, there is also a JSON 609 interface through which power commands and policies can be sent. 642 for examples of policies and instructions and
|
| H A D | ipsec_secgw.rst | 1049 policies in the following way:
|
| /dpdk/doc/guides/platform/ |
| H A D | dpaa.rst | 66 includes the queue state, RSS and other policies.
|
| /dpdk/license/ |
| H A D | README | 49 Any exception to the DPDK IP policies shall be approved by DPDK Tech Board and
|
| /dpdk/doc/guides/nics/ |
| H A D | enic.rst | 106 UCS blade servers configured with dynamic vNIC connection policies in UCSM 119 for information on configuring SR-IOV adapter policies and port profiles 122 Once the policies are in place and the host OS is rebooted, VFs should be
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_18_11.rst | 248 policies to be submitted via a FIFO using JSON formatted strings. Previously
|
| /dpdk/drivers/net/mlx5/ |
| H A D | mlx5_flow_dv.c | 17254 struct mlx5_flow_meter_policy *policies[MLX5_MTR_CHAIN_MAX_NUM]; in flow_dv_meter_sub_policy_rss_prepare() local 17263 policies[i++] = mtr_policy; in flow_dv_meter_sub_policy_rss_prepare() 17288 policies[--i], in flow_dv_meter_sub_policy_rss_prepare()
|