Home
last modified time | relevance | path

Searched refs:policies (Results 1 – 11 of 11) sorted by relevance

/f-stack/dpdk/examples/vm_power_manager/
H A Dchannel_monitor.c479 policies[i].pkt = *pkt; in update_policy()
480 get_pcpu_to_control(&policies[i]); in update_policy()
483 if (get_pfid(&policies[i]) < 0) { in update_policy()
489 policies[i].enabled = 1; in update_policy()
495 if (policies[i].enabled == 0) { in update_policy()
496 policies[i].pkt = *pkt; in update_policy()
497 get_pcpu_to_control(&policies[i]); in update_policy()
506 policies[i].enabled = 1; in update_policy()
525 policies[i].enabled = 0; in remove_policy()
1149 if (policies[j].enabled == 1) in run_channel_monitor()
[all …]
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dvm_power_management.rst34 - **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 Dipsec_secgw.rst976 policies in the following way:
/f-stack/dpdk/doc/guides/platform/
H A Ddpaa.rst66 includes the queue state, RSS and other policies.
/f-stack/dpdk/license/
H A DREADME49 Any exception to the DPDK IP policies shall be approved by DPDK Tech Board and
/f-stack/dpdk/doc/guides/prog_guide/
H A Dlink_bonding_poll_mode_drv_lib.rst78 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 Dpoll_mode_drv.rst76 …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 Denv_abstraction_layer.rst687 …5. It MUST not be used by multi-producer/consumer pthreads, whose scheduling policies are SCHED_FI…
/f-stack/dpdk/doc/guides/nics/
H A Denic.rst106 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
/f-stack/freebsd/contrib/device-tree/Bindings/arm/
H A Didle-states.yaml19 to power gating) according to OS PM policies. The CPU states representing the
/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_18_11.rst295 policies to be submitted via a FIFO using JSON formatted strings. Previously