| /openbmc/linux/Documentation/kernel-hacking/ |
| H A D | false-sharing.rst | 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
72 for false sharing:
85 False sharing could easily happen unless they are intentionally
87 critical workloads to detect false sharing affecting performance case
95 be further used to detect and pinpoint the possible false sharing
99 perf-c2c can capture the cache lines with most false sharing hits,
[all …]
|
| H A D | index.rst | 12 false-sharing
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap3/ |
| H A D | sdrc.c | 138 timings.sharing = SDRC_SHARING; in do_sdrc_init()
161 writel(timings.sharing, &sdrc_base->sharing); in do_sdrc_init()
|
| /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 | 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/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/Documentation/virt/hyperv/ |
| H A D | overview.rst | 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/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…
17 …impose any restriction or obligations with respect to the use, modification, or sharing of Results.
|
| /openbmc/u-boot/board/quipos/cairo/ |
| H A D | cairo.c | 71 timings->sharing = SAMSUNG_SHARING; in get_board_mem_timings()
|
| /openbmc/openbmc/meta-raspberrypi/dynamic-layers/openembedded-layer/recipes-devtools/python/ |
| H A D | python3-adafruit-circuitpython-busdevice_5.0.5.bb | 1 SUMMARY = "CircuitPython bus device classes to manage bus sharing."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tmate/ |
| H A D | tmate_2.4.0.bb | 1 SUMMARY = "Instant terminal sharing"
|
| /openbmc/linux/arch/arm64/boot/dts/marvell/ |
| H A D | cn9131-db.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| H A D | cn9130-db.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| H A D | cn9132-db-B.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| H A D | cn9132-db.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| H A D | cn9130-db-B.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| H A D | cn9131-db-B.dts | 15 * Since CP0 SPI1 and CP0 NAND are sharing some pins, they cannot be activated
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/gnome-user-share/ |
| H A D | gnome-user-share_47.0.bb | 1 SUMMARY = "This is gnome-user-share 43.0, a system for easy sharing of user files."
|
| /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/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/ABI/testing/ |
| H A D | sysfs-platform-hidma-mgmt | 66 sharing the same bus.
87 sharing the same bus.
|
| /openbmc/u-boot/arch/arm/include/asm/arch-omap3/ |
| H A D | sys_proto.h | 25 u32 sharing; member
|
| /openbmc/linux/drivers/net/ |
| H A D | LICENSE.SRC | 12 intent in sharing this software is to promote the productive interchange
|
| /openbmc/linux/drivers/virt/vboxguest/ |
| H A D | Kconfig | 12 for the vboxfs driver which offers folder sharing support.
|
| /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
|