/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-zoned.rst | 44 just like conventional zones. 48 1) Metadata zones: these are conventional zones used to store metadata. 52 sequential zones used exclusively to store user data. The conventional 54 Data in these zones may be directly mapped to the conventional zone, but 55 later moved to a sequential zone so that the conventional zone can be 65 1) The first block of the first conventional zone found contains the 74 mapping entry may also indicate if the zone number of a conventional 83 For a logical chunk mapped to a conventional zone, all write operations 90 conventional zone is allocated and assigned to the chunk being 105 After some time, the limited number of conventional zones available may [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/arc/ |
H A D | archs-pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
H A D | pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
/openbmc/linux/Documentation/devicetree/bindings/media/ |
H A D | fsl-vdoa.txt | 6 960 VPU to the conventional raster-scan order for scanout.
|
/openbmc/linux/drivers/isdn/ |
H A D | Kconfig | 14 (with SLIP or PPP) faster than via a conventional telephone modem
|
/openbmc/linux/fs/nilfs2/ |
H A D | Kconfig | 12 consistency like conventional LFS, it achieves quick recovery after
|
/openbmc/linux/Documentation/filesystems/ |
H A D | zonefs.rst | 38 conventional zones. Any read or write access can be executed, similarly to a 88 For conventional zones, the sub-directory "cnv" is used. This directory is 89 however created if and only if the device has usable conventional zones. If 90 the device only has a single conventional zone at sector 0, the zone will not 125 The size of conventional zone files is fixed to the size of the zone they 167 * Conventional zone aggregation: ranges of contiguous conventional zones can be 407 with the conventional zones aggregation feature enabled:: 418 conventional zone file (all conventional zones are aggregated under a single 425 This aggregated conventional zone file can be used as a regular file::
|
/openbmc/openbmc/meta-openpower/recipes-bsp/ecmd/ |
H A D | libecmd_git.bb | 35 # move all the installed files to more conventional directories.
|
/openbmc/openbmc-build-scripts/config/ |
H A D | .gitlint | 40 # contrib=contrib-title-conventional-commits,CC1 128 # [contrib-title-conventional-commits]
|
/openbmc/linux/Documentation/mm/ |
H A D | arch_pgtable_helpers.rst | 52 | pte_mkwrite_novma | Creates a writable PTE, of the conventional type | 128 | pmd_mkwrite_novma | Creates a writable PMD, of the conventional type |
|
/openbmc/linux/Documentation/admin-guide/laptops/ |
H A D | toshiba_haps.rst | 66 conventional HDD and not only SSD, or a combination of both HDD and SSD.
|
/openbmc/openbmc/poky/meta/recipes-extended/bzip2/ |
H A D | bzip2_1.0.8.bb | 3 …fman coding. Compression is generally considerably better than that achieved by more conventional \
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | kirkwood-netxbig.dtsi | 61 * switch. Thus the conventional KEY_POWER does not fit
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | kirkwood-netxbig.dtsi | 61 * switch. Thus the conventional KEY_POWER does not fit
|
/openbmc/linux/drivers/platform/surface/aggregator/ |
H A D | Kconfig | 55 not auto-detectable via the conventional means (e.g. ACPI).
|
/openbmc/linux/Documentation/block/ |
H A D | null_blk.rst | 150 The number of conventional zones to create when block device is zoned. If
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | efi-stub.rst | 22 without the use of a conventional EFI boot loader, such as grub or
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/amazon/ |
H A D | ena.rst | 192 ENA driver and device can operate in conventional or adaptive interrupt 195 **In conventional mode** the driver instructs device to postpone interrupt
|
/openbmc/u-boot/doc/ |
H A D | README.kconfig | 6 The conventional configuration was replaced by Kconfig at v2014.10-rc1 release.
|
/openbmc/linux/Documentation/misc-devices/ |
H A D | oxsemi-tornado.rst | 33 old software written for older conventional PCI Oxford Semiconductor
|
/openbmc/linux/Documentation/arch/arm/ |
H A D | kernel_user_helpers.rst | 265 - Due to the length of this sequence, this spans 2 conventional kuser
|
/openbmc/linux/Documentation/driver-api/surface_aggregator/ |
H A D | client.rst | 44 the conventional ways, e.g. as platform devices via ACPI, and devices that 93 If a device does not already exist/is not already provided via conventional
|
/openbmc/linux/Documentation/networking/ |
H A D | sfp-phylink.rst | 14 phylink supports conventional phylib-based setups, fixed link setups
|
/openbmc/qemu/docs/system/s390x/ |
H A D | vfio-ap.rst | 381 than one adapter. The APID may be specified using conventional semantics 416 usage domain. The domain number is specified using conventional semantics as 453 conventional semantics as a decimal, hexadecimal, or octal number. For
|
/openbmc/openbmc/meta-security/docs/ |
H A D | overview.txt | 159 …d to abstract away the underlying BPF based syscall filter language and present a more conventional
|