Searched full:boundary (Results 1 – 25 of 119) sorted by relevance
12345
| /Documentation/filesystems/ext4/ |
| D | verity.rst | 14 - Zero-padding to the next 65536-byte boundary. This padding need not
23 - Zero-padding to the next filesystem block boundary.
30 block boundary.
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 13 (receiving an EOF at each message boundary).
31 (receiving an EOF at each message boundary).
42 each message boundary).
53 each message boundary).
82 (receiving an EOF at each message boundary).
109 (receiving an EOF at each message boundary).
|
| D | sysfs-driver-hid-logitech-hidpp | 9 max boundary sets the range of the wheel.
|
| D | sysfs-bus-iio-light-lm3533-als | 32 These thresholds correspond to the eight zone-boundary
|
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 17 the bcachefs module boundary.
19 At the module boundary, we use bch2_err_class() to convert to a standard error
|
| /Documentation/filesystems/ |
| D | romfs.rst | 72 : : padded to 16 byte boundary.
91 must begin on a 16 byte boundary::
105 : : padded to 16 byte boundary
110 Since the file headers begin always at a 16 byte boundary, the lowest
149 padded to an 1024 byte boundary.
178 boundary, it is currently possibly suboptimal to read or execute files
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 69 boundary within the containing section or image. For example ‘align =
70 <16>’ means that the entry will start on a 16-byte boundary. This may
102 Some entries require that they end on an alignment boundary,
|
| /Documentation/networking/ |
| D | radiotap-headers.rst | 57 - the arguments must be aligned to a boundary of the argument size using
58 padding. So a u16 argument must start on the next u16 boundary if it isn't
59 already on one, a u32 must start on the next u32 boundary and so on.
|
| /Documentation/ABI/removed/ |
| D | sysfs-bus-nfit | 15 This property indicates the boundary at which the NVDIMM may
|
| /Documentation/devicetree/bindings/hwinfo/ |
| D | renesas,prr.yaml | 14 Most Renesas ARM SoCs have a Product Register or Boundary Scan ID
|
| /Documentation/arch/mips/ |
| D | booting.rst | 21 aligned on a 64 bit boundary.
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-y12i.rst | 27 pixels cross the byte boundary and have a ratio of 3 bytes for each
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | gianfar.rst | 43 to align the IP header to a 16-byte boundary, when supported by
|
| /Documentation/hwmon/ |
| D | gsc-hwmon.rst | 52 pwm1_auto_point[1-6]_temp Temperature boundary.
|
| /Documentation/fb/ |
| D | pxafb.rst | 121 b. line length of overlay(s) must be on a 32-bit word boundary,
128 word boundary, otherwise the fb_check_var() will just fail.
|
| D | matroxfb.rst | 223 cross4MB enables that pixel line can cross 4MB boundary. It is default for
225 nocross4MB pixel line must not cross 4MB boundary. It is default for
265 upper:X top boundary: lines between end of VSYNC pulse and start of first
267 lower:X bottom boundary: lines between end of picture and start of VSYNC
271 left:X left boundary: pixels between end of HSYNC pulse and first pixel.
273 right:X right boundary: pixels between end of picture and start of HSYNC
|
| /Documentation/devicetree/bindings/arm/ |
| D | fsl.yaml | 256 - boundary,imx6q-nitrogen6_max
257 - boundary,imx6q-nitrogen6_som2
258 - boundary,imx6q-nitrogen6x
420 - boundary,imx6qp-nitrogen6_max
421 - boundary,imx6qp-nitrogen6_som2
455 - boundary,imx6dl-nit6xlite # Boundary Devices Nitrogen6 Lite
456 - boundary,imx6dl-nitrogen6x # Boundary Devices Nitrogen6x
626 - boundary,imx6sx-nitrogen6sx
869 - boundary,imx7d-nitrogen7
936 - boundary,imx8mm-nitrogen8mm # i.MX8MM Nitrogen Board
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 67 the boundary and forbid creating such VMAs once MPX is enabled.
|
| /Documentation/arch/powerpc/ |
| D | vcpudispatch_stats.rst | 37 (next numa boundary)
|
| /Documentation/misc-devices/ |
| D | c2port.rst | 46 boundary-scan testing on low pin-count Silicon Labs devices. Currently
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-mmap.rst | 106 they are too large, or not aligned on a ``PAGESIZE`` boundary.)
|
| /Documentation/arch/arm/ |
| D | booting.rst | 142 A safe location is just above the 128MiB boundary from start of RAM.
158 be loaded just above the 128MiB boundary from the start of RAM as
|
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 119 byte boundary.
152 octet boundary. The tag types defined in this document contain alignment
236 is to align the category bitmap field on an even octet boundary. This will
322 is to align the category field on an even octet boundary. This will
385 is to align the category range field on an even octet boundary. This will
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 408 …padded to the most significant bit side till the next byte boundary. Next, if the output element s…
484 page size code for the page boundary checking the guest wants
575 … page size code for the page boundary checking the guest wants
596 …scan range commands, the boundary conditions can be specified as greater-than-or-equal-to a value,…
597 than-or-equal-to a value, or both by using two boundary values.
672 boundary. The value of this field is the number of bytes in the
678 boundary. The value of this field is the number of bytes in the
814 page size code for the page boundary checking the guest wants
1042 size associated with a given address. No data will have been read or written past the page boundary…
1224 EBADALIGN CCB array is not on a 64-byte boundary, or the array length is not a multiple
|
| /Documentation/admin-guide/ |
| D | cgroup-v2.rst | 1256 is within its effective min boundary, the cgroup's memory
1259 is invoked. Above the effective min boundary (or
1260 effective low boundary if it is higher), pages are reclaimed
1264 Effective min boundary is limited by memory.min values of
1282 cgroup is within its effective low boundary, the cgroup's
1285 Above the effective low boundary (or
1286 effective min boundary if it is higher), pages are reclaimed
1290 Effective low boundary is limited by memory.low values of
1305 over the high boundary, the processes of the cgroup are
1405 the low boundary. This usually indicates that the low
[all …]
|
12345