Searched full:disruption (Results 1 – 20 of 20) sorted by relevance
36 name suggests, this dump is created without causing any disruption to
119 * left to minimize unnecessary disruption for users of libbpf. But they
27 - can be implemented immediately with minimal disruption of other
84 whole or in part, we ask that you do so in a way that minimizes disruption
74 persist across a power-session disruption.
19 * disruption.
242 minimal disruption by using the lookup table. When the set of
854 /* Restore the default value to minimise disruption */ in test_ctl_write_valid()1066 /* Restore the default value to minimise disruption */ in test_ctl_write_invalid()
8 disruption in flow routing across changes to the group composition and
505 * disruption to isochronous transfers. But in the event in bm_work()
658 * implement this so there is no disruption in translation. This can only be
609 * disruption to any unrelated chips that might be already using in vc5_clk_out_prepare()
1088 * To minimise LRU disruption, the caller can indicate with in isolate_migratepages_block()
1603 * To avoid unnecessary video disruption, only write the new in video_proc_write()
844 * because it can cause significant disruption in wil_cfg80211_change_iface()
2311 invalid causing disruption to tasks running in those child
1041 "Avoid sending a force load request to prevent disruption of active PFs\n"); in qed_mcp_load_req()
2237 "Skip Marker due to disruption. Nexus=%ld:%06x:%llu.\n", in __qla2x00_async_tm_cmd()2295 "Unable to acquire TM resource due to disruption.\n"); in qla_get_tmf()
3072 * Also need to correct the disruption we've added to guarantee this in bnx2x_mcast_hdl_pending_set_e2_convert()
4742 Unfortunately, a disruption in the directory graph pointers result in a