| /linux/tools/testing/selftests/cgroup/ |
| H A D | memcg_protection.m | 6 % hierarchy to illustrate how overcommitted protection spreads among siblings 9 % Simulation assumes siblings consumed the initial amount of memory (w/out 16 % n vector nominal protection of siblings set at the given level (memory.low) 48 siblings = sum(u); variable 52 e = protected * min(1, E / siblings); % normalize overcommit 55 unclaimed = max(0, E - siblings); 56 parent_overuse = sum(c) - siblings; 79 % XXX here I do parallel reclaim of all siblings
|
| /linux/drivers/infiniband/hw/irdma/ |
| H A D | ws.c | 133 list_for_each_entry(node, &parent->child_list_head, siblings) { in ws_find_node() 139 list_for_each_entry(node, &parent->child_list_head, siblings) { in ws_find_node() 214 list_del(&tc_node->siblings); in irdma_remove_leaf() 219 list_del(&vsi_node->siblings); in irdma_remove_leaf() 295 list_add(&vsi_node->siblings, &ws_tree_root->child_list_head); in irdma_ws_add() 322 list_add(&tc_node->siblings, &vsi_node->child_list_head); in irdma_ws_add() 356 list_del(&tc_node->siblings); in irdma_ws_add() 362 list_del(&vsi_node->siblings); in irdma_ws_add()
|
| H A D | ws.h | 19 struct list_head siblings; member
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | selftest_execlists.c | 3713 struct intel_engine_cs **siblings, in nop_virtual_engine() argument 3730 ve[n] = intel_engine_create_virtual(siblings, nsibling, 0); in nop_virtual_engine() 3841 struct intel_engine_cs **siblings, in __select_siblings() argument 3854 siblings[n++] = gt->engine_class[class][inst]; in __select_siblings() 3863 struct intel_engine_cs **siblings) in select_siblings() argument 3865 return __select_siblings(gt, class, siblings, NULL); in select_siblings() 3871 struct intel_engine_cs *siblings[MAX_ENGINE_INSTANCE + 1]; in live_virtual_engine() local 3892 nsibling = select_siblings(gt, class, siblings); in live_virtual_engine() 3897 err = nop_virtual_engine(gt, siblings, nsibling, in live_virtual_engine() 3903 err = nop_virtual_engine(gt, siblings, nsibling, n, CHAIN); in live_virtual_engine() [all …]
|
| H A D | intel_engine_cs.c | 2449 intel_engine_create_virtual(struct intel_engine_cs **siblings, in intel_engine_create_virtual() argument 2456 return intel_context_create(siblings[0]); in intel_engine_create_virtual() 2458 GEM_BUG_ON(!siblings[0]->cops->create_virtual); in intel_engine_create_virtual() 2459 return siblings[0]->cops->create_virtual(siblings, count, flags); in intel_engine_create_virtual()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 100 siblings of a core such that all the selected tasks running on a core are 107 the sibling has the task enqueued. For rest of the siblings in the core, 112 Once a task has been selected for all the siblings in the core, an IPI is sent to 113 siblings for whom a new task was selected. Siblings on receiving the IPI will 125 siblings could be forced to select a lower priority task if the highest 157 and are considered system-wide trusted. The forced-idling of siblings running 174 the siblings to switch to the new task. But there could be hardware delays in 176 cause an attacker task to start running on a CPU before its siblings receive the 177 IPI. Even though cache is flushed on entry to user mode, victim tasks on siblings 185 Core scheduling cannot protect against MDS attacks between the siblings [all …]
|
| H A D | attack_vector_controls.rst | 125 techniques are used to prevent untrusted workloads from running on SMT siblings.
|
| /linux/drivers/gpio/ |
| H A D | gpio-virtuser.c | 1010 struct list_head siblings; member 1029 struct list_head siblings; member 1372 list_for_each_entry(lookup, &dev->lookup_list, siblings) in gpio_virtuser_get_lookup_count() 1397 list_for_each_entry(lookup, &dev->lookup_list, siblings) { in gpio_virtuser_make_lookup_table() 1399 list_for_each_entry(entry, &lookup->entry_list, siblings) { in gpio_virtuser_make_lookup_table() 1438 list_for_each_entry(lookup, &dev->lookup_list, siblings) in gpio_virtuser_make_device_swnode() 1527 list_for_each_entry(lookup, &dev->lookup_list, siblings) { in gpio_virtuser_device_lockup_configfs() 1528 list_for_each_entry(entry, &lookup->entry_list, siblings) { in gpio_virtuser_device_lockup_configfs() 1590 list_del(&entry->siblings); in gpio_virtuser_lookup_entry_config_group_release() 1630 list_add_tail(&entry->siblings, &lookup->entry_list); in gpio_virtuser_make_lookup_entry_group() [all …]
|
| /linux/drivers/scsi/ |
| H A D | scsi.c | 827 struct list_head *list = (prev ? &prev->siblings : &shost->__devices); in __scsi_iterate_devices() 833 next = list_entry(list->next, struct scsi_device, siblings); in __scsi_iterate_devices() 981 list_for_each_entry(sdev, &shost->__devices, siblings) { in __scsi_device_lookup()
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_epb.rst | 40 example, SMT siblings or cores in one package). For this reason, updating the
|
| H A D | intel_pstate.rst | 358 performant CPUs are used when the other ones are fully loaded. SMT siblings 362 placed on the SMT siblings of physical cores only after all physical cores are 369 siblings are hard to determine, hybrid processors without SMT can be handled in 645 is requesting higher performance, the other siblings will get higher
|
| H A D | intel_idle.rst | 295 ``CC3``), which happens if all of the logical CPUs (SMT siblings) in that core
|
| /linux/drivers/scsi/libsas/ |
| H A D | sas_expander.c | 856 list_add_tail(&child->siblings, &parent_ex->children); in sas_ex_discover_end_dev() 964 list_add_tail(&child->siblings, &parent->ex_dev.children); in sas_ex_discover_expander() 1092 list_for_each_entry(child, &ex->children, siblings) { in sas_check_level_subtractive_boundary() 1817 list_for_each_entry(ch, &ex->children, siblings) { in sas_find_bcast_dev() 1833 list_for_each_entry_safe(child, n, &ex->children, siblings) { in sas_unregister_ex_tree() 1851 &ex_dev->children, siblings) { in sas_unregister_devs_sas_addr() 1885 list_for_each_entry(child, &ex_root->children, siblings) { in sas_discover_bfs_by_root_level() 1936 list_for_each_entry(child, &dev->ex_dev.children, siblings) { in sas_discover_new()
|
| H A D | sas_internal.h | 198 INIT_LIST_HEAD(&dev->siblings); in sas_alloc_device()
|
| H A D | sas_discover.c | 321 list_del_init(&dev->siblings); in sas_unregister_common_dev()
|
| /linux/Documentation/scsi/ |
| H A D | scsi-generic.rst | 13 is more generalized (but lower level) than its siblings and tends to be
|
| /linux/net/sched/ |
| H A D | sch_hfsc.c | 123 struct list_head siblings; /* sibling classes */ member 707 * among the siblings. this is analogous to in init_vf() 846 list_for_each_entry(p, &cl->children, siblings) { in hfsc_adjust_levels() 1078 list_add_tail(&cl->siblings, &parent->children); in hfsc_change_class() 1117 list_del(&cl->siblings); in hfsc_delete_class()
|
| /linux/Documentation/virt/ |
| H A D | ne_overview.rst | 52 An enclave runs on dedicated cores. CPU 0 and its CPU siblings need to remain
|
| /linux/Documentation/power/powercap/ |
| H A D | dtpm.rst | 76 …e have a weight on a 2^10 basis reflecting the percentage of power consumption along the siblings::
|
| /linux/Documentation/networking/devlink/ |
| H A D | ice.rst | 421 - allows for usage of strict priority arbiter among siblings. This 429 siblings. This arbitration scheme can be used simultaneously with
|
| /linux/drivers/target/ |
| H A D | target_core_pscsi.c | 495 list_for_each_entry(sd, &sh->__devices, siblings) { in pscsi_configure_device()
|
| /linux/Documentation/i2c/ |
| H A D | i2c-topology.rst | 100 mux-locked muxes that are not siblings, when there are address
|
| /linux/Documentation/arch/x86/ |
| H A D | topology.rst | 118 The number of online threads is also printed in /proc/cpuinfo "siblings."
|
| /linux/Documentation/driver-api/ |
| H A D | device_link.rst | 14 mere parent/child relationship, e.g. between siblings, and have the
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cpusets.rst | 563 is idle while CPU X and the siblings are busy, scheduler can't migrate 577 1 search siblings (hyperthreads in a core).
|