| /openbmc/linux/Documentation/kernel-hacking/ |
| H A D | false-sharing.rst | 4 False Sharing
7 What is False Sharing
9 False sharing is related with cache mechanism of maintaining the data
44 reload the whole cache line over and over due to the 'sharing', even
48 false sharing. One of these is a rw_semaphore 'mmap_lock' inside
52 There are two key factors for a harmful false sharing:
58 The sharing could be from totally unrelated kernel components, or
62 False Sharing Pitfalls
72 for false sharing:
85 False sharing could easily happen unless they are intentionally
[all …]
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | redundancy.hpp | 12 Sharing, enumerator
21 {RedundancyType::Sharing, "Sharing"},
|
| /openbmc/linux/Documentation/virt/hyperv/ |
| H A D | overview.rst | 61 Sharing Memory
64 on sharing memory. Such sharing is generally accomplished as
82 * Linux can later revoke sharing it has previously established by
105 the time that Linux originally establishes the sharing and the
107 revokes the sharing, in which case Hyper-V removes the overlay page,
116 guest VMs, so Linux code must individually revoke all sharing before
|
| /openbmc/linux/drivers/net/ethernet/mscc/ |
| H A D | ocelot_devlink.c | 23 * PRIO_SHR: sharing watermark per QoS class across all ports
25 * COL_SHR: sharing watermark per color (drop precedence) across all ports
127 /* Sharing Watermarks
248 * reservations and rely only on the sharing watermark for frames with drop
270 /* We want the sharing watermarks to consume all nonreserved resources, for
274 * The switch has 10 sharing watermarks per lookup: 8 per traffic class and 2
276 * The trouble with configuring these sharing watermarks is that:
278 * (a) all 8 per-TC sharing watermarks to the max
279 * (b) all 2 per-color sharing watermarks to the max
281 * (a) all 8 per-TC sharing watermarks to "max / 8"
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CDLA-Permissive-2.0 | 9 …s not impose any restriction on a Data Recipient's use, modification, or sharing of any portions o…
11 2. Conditions for Sharing Data
17 …impose any restriction or obligations with respect to the use, modification, or sharing of Results.
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 14 by sharing the data common between them. But it can be useful to any
27 be swapped out just like other user pages (but sharing is broken when they
99 sharing of setting 1 (default). You may wish to compare how
133 Maximum sharing allowed for each KSM page. This enforces a
167 how many more sites are sharing them i.e. how much saved
187 sharing, but a high ratio of ``pages_unshared`` to ``pages_sharing``
|
| /openbmc/linux/net/9p/ |
| H A D | Kconfig | 7 tristate "Plan 9 Resource Sharing Support (9P2000)"
10 Plan 9 resource sharing via the 9P2000 protocol.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | wmi.rst | 10 it has some issues with multiple WMI devices and events sharing the same GUIDs
13 WMI devices sharing GUIDs and/or notification IDs. Drivers can then register
|
| H A D | dma-buf.rst | 1 Buffer Sharing and Synchronization (dma-buf)
4 The dma-buf subsystem provides the framework for sharing buffers for
21 buffer sharing API, how to use it for exporting and using shared buffers.
23 Any device driver which wishes to be a part of DMA buffer sharing, can do so as
33 - allows other users to share the buffer by using dma_buf sharing APIs,
42 - is one of (many) sharing users of the buffer.
49 Any exporters or users of the dma-buf buffer sharing framework must have a
|
| /openbmc/linux/drivers/opp/ |
| H A D | cpu.c | 185 /* Mark opp-table as multiple CPUs are sharing it now */ in dev_pm_opp_set_sharing_cpus()
196 * dev_pm_opp_get_sharing_cpus() - Get cpumask of CPUs sharing OPPs with @cpu_dev
198 * @cpumask: cpumask to update with information of sharing CPUs
200 * This updates the @cpumask with CPUs that are sharing OPPs with @cpu_dev.
|
| /openbmc/linux/fs/9p/ |
| H A D | Kconfig | 3 tristate "Plan 9 Resource Sharing Support (9P2000)"
8 Plan 9 resource sharing via the 9P2000 protocol.
|
| /openbmc/linux/include/linux/ |
| H A D | cacheinfo.h | 30 * lines sharing the same index
33 * @physical_line_partition: number of physical cache lines sharing the
36 * @shared_cpu_map: logical cpumask representing all the cpus sharing
|
| H A D | kvm_irqfd.h | 26 * List of resampling struct _irqfd objects sharing this gsi.
32 * Entry in list of kvm->irqfd.resampler_list. Use for sharing
|
| /openbmc/linux/arch/s390/include/asm/ |
| H A D | mmu.h | 37 * The mmu context allows COW-sharing of memory pages (KSM, zeropage).
38 * Note that COW-sharing during fork() is currently always allowed.
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | cs35l32.txt | 34 - cirrus,sdout-share : SDOUT sharing. Determines whether one or two CS35L32
35 devices are on board sharing SDOUT.
|
| /openbmc/linux/tools/testing/selftests/mm/ |
| H A D | hugepage-mremap.c | 11 * To make sure the test triggers pmd sharing and goes through the 'unshare'
131 /* mmap to a PUD aligned address to hopefully trigger pmd sharing. */ in main()
141 /* mmap again to a dummy address to hopefully trigger pmd sharing. */ in main()
|
| /openbmc/linux/drivers/net/ethernet/mellanox/mlx5/core/en/ |
| H A D | tc_priv.h | 83 /* flows sharing the same reformat object - currently mpls decap */
87 /* flows sharing same route entry */
98 struct list_head hairpin; /* flows sharing the same hairpin */
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A D | rsdumpinfo.c | 35 {ACPI_RSD_2BITFLAG, ACPI_RSD_OFFSET(irq.shareable), "Sharing",
225 {ACPI_RSD_2BITFLAG, ACPI_RSD_OFFSET(extended_irq.shareable), "Sharing",
258 {ACPI_RSD_2BITFLAG, ACPI_RSD_OFFSET(gpio.shareable), "Sharing",
288 {ACPI_RSD_1BITFLAG, ACPI_RSD_OFFSET(pin_function.shareable), "Sharing",
328 {ACPI_RSD_1BITFLAG, ACPI_RSD_OFFSET(pin_config.shareable), "Sharing",
374 "Sharing", acpi_gbl_shr_decode},
396 "Sharing", acpi_gbl_shr_decode},
|
| /openbmc/linux/tools/testing/selftests/drivers/net/netdevsim/ |
| H A D | udp_tunnel_nic.sh | 456 msg="table sharing - share"
460 msg="table sharing - overflow"
462 msg="table sharing - overflow v6"
514 msg="table sharing - share"
518 msg="table sharing - overflow"
520 msg="table sharing - overflow v6"
805 pfx="table sharing"
|
| /openbmc/linux/Documentation/netlink/specs/ |
| H A D | ovs_datapath.yaml | 31 name: tc-recirc-sharing
32 doc: Allow tc offload recirc sharing
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Redundancy.v1_4_2.json | 174 "Sharing",
182 …"Sharing": "Multiple units contribute or share such that operation will continue, but at a reduced… string
194 "Sharing",
202 …"Sharing": "Multiple units contribute or share such that operation will continue, but at a reduced… string
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Redundancy.v1_4_2.json | 174 "Sharing",
182 …"Sharing": "Multiple units contribute or share such that operation will continue, but at a reduced… string
194 "Sharing",
202 …"Sharing": "Multiple units contribute or share such that operation will continue, but at a reduced… string
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a
20 stateless or ephemeral guests, and sharing a directory between guests.
|
| /openbmc/linux/Documentation/mm/ |
| H A D | ksm.rst | 30 When the sharing passes this threshold, KSM adds a second dimension to
48 (i.e. virtual mappings) that are sharing the page, which is in turn
|
| /openbmc/u-boot/fs/ext4/ |
| H A D | ext4_journal.h | 82 __be32 s_nr_users; /* Nr of filesystems sharing log */
94 __u8 s_users[16 * 48]; /* ids of all fs'es sharing the log */
|