Home
last modified time | relevance | path

Searched full:layouts (Results 1 – 25 of 124) sorted by relevance

12345

/linux/Documentation/admin-guide/nfs/
H A Dpnfs-scsi-server.rst6 This document describes support for pNFS SCSI layouts in the Linux NFS server.
7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,
9 also hands out layouts to the clients so that they can directly access the
12 To use pNFS SCSI layouts with the Linux NFS server, the exported file
13 system needs to support the pNFS SCSI layouts (currently just XFS), and the
H A Dpnfs-block-server.rst7 to handling all the metadata access to the NFS export also hands out layouts
11 To use pNFS block layouts with the Linux NFS server the exported file
12 system needs to support the pNFS block layouts (currently just XFS), and the
/linux/Documentation/devicetree/bindings/nvmem/layouts/
H A Dnvmem-layout.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
7 title: NVMEM (Non Volatile Memory) layouts
15 Most NVMEM layouts are static and thus do not require additional description
16 besides the bytes/bits offset and length. Other layouts can be less statically
H A Dfixed-cell.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-cell.yaml#
H A Dfixed-layout.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-layout.yaml#
/linux/fs/nfsd/
H A DKconfig98 bool "NFSv4.1 server support for pNFS block layouts"
103 This option enables support for the exporting pNFS block layouts
111 bool "NFSv4.1 server support for pNFS SCSI layouts"
116 This option enables support for the exporting pNFS SCSI layouts
125 bool "NFSv4.1 server support for pNFS Flex File layouts"
130 layouts in the kernel's NFS server. The pNFS Flex File layout
/linux/Documentation/driver-api/
H A Dnvmem.rst183 8. NVMEM layouts
186 NVMEM layouts are yet another mechanism to create cells. With the device
191 be added accordingly. Layouts let you read the content of the NVMEM device
194 Another use case for layouts is the post processing of cells. With layouts,
/linux/Documentation/devicetree/bindings/nvmem/
H A Dnvmem-deprecated-cells.yaml13 Before introducing NVMEM layouts all NVMEM (fixed) cells were defined
21 - $ref: layouts/fixed-cell.yaml
H A Dst,stm32-romem.yaml36 $ref: layouts/fixed-cell.yaml
/linux/drivers/net/ethernet/sfc/
H A Dfw_formats.h14 /* Header layouts of firmware update images recognised by Efx NICs.
15 * The sources-of-truth for these layouts are AMD internal documents
/linux/Documentation/filesystems/nfs/
H A Dpnfs.rst5 The are several inter-related caches. We have layouts which can
8 can be referenced by multiple layouts. To keep all of this straight,
/linux/include/uapi/drm/
H A Ddrm_fourcc.h62 * match only a single modifier. A modifier must not be a subset of layouts of
72 * latter is AFBC, where the ABGR layouts are preferred over ARGB layouts.
504 * for layouts which are common across multiple vendors. To preserve
510 * generic layouts (such as pixel re-ordering), which may have
986 * GPUs with different layouts.
1023 * with block-linear layouts, is remapped within drivers to the value 0xfe,
1470 /* Amlogic FBC Layouts */
1560 * Apple GPU-tiled layouts.
1583 * These layouts fundamentally do not have meaningful strides. No matter how we
1584 * specify strides for these layouts, userspace unaware of Apple image layouts
[all …]
/linux/tools/virtio/ringtest/
H A DREADME1 Partial implementation of various ring layouts, useful to tune virtio design.
/linux/drivers/nvmem/layouts/
H A DMakefile3 # Makefile for nvmem layouts.
/linux/arch/parisc/include/asm/
H A Dsparsemem.h5 /* We have these possible memory map layouts:
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-raid.rst121 then the layouts for 2, 3 and 4 devices are:
138 If 'raid10_copies 2' and 'raid10_format far', then the layouts
155 layouts for 2, 3 and 4 devices are:
169 Here we see layouts closely akin to 'RAID1E - Integrated
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dubi-volume.yaml28 $ref: /schemas/nvmem/layouts/nvmem-layout.yaml#
/linux/drivers/md/
H A Draid0.h17 * The layouts are identical when there is only one zone (all
/linux/Documentation/devicetree/bindings/display/
H A Dlvds.yaml20 data formats and layouts is used to drive LVDS displays.
/linux/Documentation/userspace-api/media/v4l/
H A Dpixfmt-yuv-planar.rst392 The layouts of the luma and chroma planes are identical.
400 tiles is stored in linear order. The layouts of the luma and chroma
421 aligned to a multiple of 4. The layouts of the luma and chroma planes are
426 aligned to a multiple of 16. The layouts of the luma and chroma planes are
431 aligned to a multiple of 32. The layouts of the luma and chroma planes are
437 The layouts of the luma and chroma planes are identical.
467 The layouts of the luma and chroma planes are identical.
980 a multiple of 4. The layouts of the luma and chroma planes are identical.
/linux/include/linux/
H A Delfcore-compat.h10 * Make sure these layouts match the linux/elfcore.h native definitions.
/linux/arch/sparc/include/uapi/asm/
H A Ductx.h3 * uctx.h: Sparc64 {set,get}context() register state layouts.
/linux/Documentation/input/
H A Dgamepad.rst112 BTN_EAST. For vertical layouts, the upper button is BTN_EAST. For
113 horizontal layouts, the button more on the right is BTN_EAST.
/linux/include/drm/
H A Ddrm_framebuffer.h163 * storage buffer object. For tiled layouts this generally means its
174 * tiling, or also special layouts (like compression) of auxiliary
/linux/rust/kernel/mm/
H A Dmmput_async.rs65 // SAFETY: The layouts and invariants are compatible. in into_mmput_async()

12345