Searched +full:32 +full:kb (Results 1 – 25 of 63) sorted by relevance
123
| /Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 34 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
46 hugetlb.64KB.limit_in_bytes
47 hugetlb.64KB.max_usage_in_bytes
48 hugetlb.64KB.numa_stat
49 hugetlb.64KB.usage_in_bytes
50 hugetlb.64KB.failcnt
51 hugetlb.64KB.rsvd.limit_in_bytes
52 hugetlb.64KB.rsvd.max_usage_in_bytes
53 hugetlb.64KB.rsvd.usage_in_bytes
54 hugetlb.64KB.rsvd.failcnt
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | redboot-fis.yaml | 14 32 KB in size.
28 device. On a flash memory with 32KB eraseblocks, 0 means the first
|
| /Documentation/arch/arm64/ |
| D | memory.rst | 9 tables with a 4KB page size and up to 3 levels with a 64KB page size.
12 with the 4KB page configuration, allowing 39-bit (512GB) or 48-bit
14 64KB pages, only 2 levels of translation tables, allowing 42-bit (4TB)
18 only available when running with a 64KB page size and expands the
27 AArch64 Linux memory layout with 4KB pages + 4 levels (48-bit)::
33 [ffff600000000000 ffff7fffffffffff] 32TB [kasan shadow region]
44 AArch64 Linux memory layout with 64KB pages + 3 levels (52-bit with HW support)::
61 Translation table lookup with 4KB pages::
64 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
76 Translation table lookup with 64KB pages::
[all …]
|
| /Documentation/translations/zh_TW/arch/arm64/ |
| D | memory.txt | 37 頁大小爲 4KB 的 4 級轉換表和頁大小爲 64KB 的 3 級轉換表。
39 AArch64 Linux 使用 3 級或 4 級轉換表，其頁大小配置爲 4KB，對於用戶和內核
49 AArch64 Linux 在頁大小爲 4KB，並使用 3 級轉換表時的內存佈局：
57 AArch64 Linux 在頁大小爲 4KB，並使用 4 級轉換表時的內存佈局：
65 AArch64 Linux 在頁大小爲 64KB，並使用 2 級轉換表時的內存佈局：
73 AArch64 Linux 在頁大小爲 64KB，並使用 3 級轉換表時的內存佈局：
84 4KB 頁大小的轉換表查找：
87 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
99 64KB 頁大小的轉換表查找：
102 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
|
| /Documentation/translations/zh_CN/arch/arm64/ |
| D | memory.txt | 33 页大小为 4KB 的 4 级转换表和页大小为 64KB 的 3 级转换表。
35 AArch64 Linux 使用 3 级或 4 级转换表，其页大小配置为 4KB，对于用户和内核
45 AArch64 Linux 在页大小为 4KB，并使用 3 级转换表时的内存布局：
53 AArch64 Linux 在页大小为 4KB，并使用 4 级转换表时的内存布局：
61 AArch64 Linux 在页大小为 64KB，并使用 2 级转换表时的内存布局：
69 AArch64 Linux 在页大小为 64KB，并使用 3 级转换表时的内存布局：
80 4KB 页大小的转换表查找：
83 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
95 64KB 页大小的转换表查找：
98 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 49 shall implement "true random writes with 2KB granularity", which means
51 2KB on such a disc. For example, it should be possible to do::
59 host to perform aligned writes at 32KB boundaries. Other drives do
61 writes are not 32KB aligned.
92 device with a 2KB block size, you can put any filesystem you like on
|
| /Documentation/arch/arm/stm32/ |
| D | stm32f746-overview.rst | 12 - 1MB internal flash, 320KBytes internal RAM (+4KB of backup SRAM)
19 - Several 16 & 32 bits general purpose timers
30 .. _STM32F746: http://www.st.com/content/st_com/en/products/microcontrollers/stm32-32-bit-arm-corte…
|
| D | stm32f769-overview.rst | 12 - 2MB internal flash, 512KBytes internal RAM (+4KB of backup SRAM)
19 - Several 16 & 32 bits general purpose timers
32 .. _STM32F769: http://www.st.com/content/st_com/en/products/microcontrollers/stm32-32-bit-arm-corte…
|
| /Documentation/fb/ |
| D | tridentfb.rst | 17 The driver supports 8, 16 and 32 bits per pixel depths.
54 memsize integer value in KB, use if your card's memory size is misdetected.
57 memdiff integer value in KB, should be nonzero if your card reports
69 bpp bits per pixel (8,16 or 32)
|
| /Documentation/arch/x86/ |
| D | zero-page.rst | 6 The additional fields in struct boot_params as a part of 32-bit boot
28 0C0/004 ALL ext_ramdisk_image ramdisk_image high 32bits
29 0C4/004 ALL ext_ramdisk_size ramdisk_size high 32bits
30 0C8/004 ALL ext_cmd_line_ptr cmd_line_ptr high 32bits
33 1C0/020 ALL efi_info EFI 32 information (struct efi_info)
34 1E0/004 ALL alt_mem_k Alternative mem check, in KB
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 138 reg = <0xbfdf0000 0x10000>; /* 64kB */
139 console-size = <0x8000>; /* 32kB */
140 record-size = <0x400>; /* 1kB */
|
| /Documentation/devicetree/bindings/misc/ |
| D | intel,ixp4xx-ahb-queue-manager.yaml | 15 an 8KB embedded SRAM along with hardware pointers. It is used by both
34 - description: Interrupt for queues 32-63
|
| /Documentation/staging/ |
| D | lzo.rst | 134 2-byte block from the dictionary within a 1kB distance. It is worth
139 0 0 0 0 D D S S (0..15) : copy 2 bytes from <= 1kB distance
147 dictionary from a 2..3kB distance, and must be interpreted like this :
149 0 0 0 0 D D S S (0..15) : copy 3 bytes from 2..3 kB distance
156 Copy of a block within 16..48kB distance (preferably less than 10B)
172 0 0 1 L L L L L (32..63)
173 Copy of small block within 16kB distance (preferably less than 34B)
180 Copy 3-4 bytes from block within 2kB distance
187 Copy 5-8 bytes from block within 2kB distance
|
| /Documentation/mm/ |
| D | page_tables.rst | 29 With a page granularity of 4KB and a address range of 32 bits, pfn 0 is at
31 and so on until we reach pfn 0xfffff at 0xfffff000. With 16KB pages pfs are
34 As you can see, with 4KB pages the page base address uses bits 12-31 of the
39 sizes. When Linux was created, 4KB pages and a single page table called
92 A typical example is that the `pteval_t` is a 32- or 64-bit value with the
254 Linux supports larger page sizes than the usual 4KB (i.e., the so called
|
| D | vmemmap_dedup.rst | 20 currently supported. Since the base page size on x86 is 4KB, a 2MB HugeTLB page
41 | x86-64 | 4KB | 2MB | 1GB | | |
43 | | 4KB | 64KB | 2MB | 32MB | 1GB |
45 | arm64 | 16KB | 2MB | 32MB | 1GB | |
47 | | 64KB | 2MB | 512MB | 16GB | |
|
| /Documentation/translations/zh_TW/arch/arm/ |
| D | Booting | 147 基地址的前 16KB RAM 空間來保存頁表。建議將映像置於 RAM 的 32KB 處。
|
| /Documentation/translations/zh_CN/arch/arm/ |
| D | Booting | 147 基地址的前 16KB RAM 空间来保存页表。建议将映像置于 RAM 的 32KB 处。
|
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 94 filesystems with 4 KB block size, a single metablock group partition
100 to the hard limit 2^32, allowing support for a 512PiB filesystem.
110 a 1KB block size, and 64 block groups for filesystems with a 4KB
|
| /Documentation/filesystems/ |
| D | proc.rst | 183 VmPeak: 5004 kB
184 VmSize: 5004 kB
185 VmLck: 0 kB
186 VmHWM: 476 kB
187 VmRSS: 476 kB
188 RssAnon: 352 kB
189 RssFile: 120 kB
190 RssShmem: 4 kB
191 VmData: 156 kB
192 VmStk: 88 kB
[all …]
|
| /Documentation/admin-guide/ |
| D | bootconfig.rst | 173 The size and checksum fields are unsigned 32bit little endian value.
268 Currently the maximum config size size is 32KB and the total key-words (not
274 will be under 100 entries and smaller than 8KB, so it would be enough.
276 size is smaller than 32KB. (Note that this maximum size is not including
|
| D | pstore-blk.rst | 63 where SSSSSSSS is a zero-filled hex representation of the 32-bit
78 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4.
90 The chunk size in KB for pmsg front-end. It **MUST** be a multiple of 4.
102 The chunk size in KB for console front-end. It **MUST** be a multiple of 4.
113 The chunk size in KB for ftrace front-end. It **MUST** be a multiple of 4.
|
| /Documentation/admin-guide/mm/ |
| D | transhuge.rst | 52 memory (for example 16K, 32K, 64K, etc). These THPs continue to be
115 echo always >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
116 echo madvise >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
117 echo never >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
124 echo always >/sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
129 echo inherit >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
133 echo inherit >/sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
311 For example, the following will set 16K, 32K, 64K THP to ``always``,
370 '/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/shmem_enabled',
397 transparent_hugepage/hugepages-<size>kB/enabled values and tmpfs mount
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | mm.rst | 20 from TB to GB and then MB/KB.
47 ffffc90000000000 | -55 TB | ffffe8ffffffffff | 32 TB | vmalloc/ioremap space (vmalloc_base)
70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
104 …ff11000000000000 | -59.75 PB | ff90ffffffffffff | 32 PB | direct mapping of all physical memory…
129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 19 - interrupts : each one of the interrupts here is one entry per 32 MSIs,
28 Each available range must begin and end on a multiple of 32 (i.e.
30 MPIC v4.3 does not support this property because the 32 interrupts of an
103 restrictions, it is usually impossible to create a 4KB subwindow that
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | xlnx,zynqmp-r5fss.yaml | 72 Each RPU contains one 64KB memory and two 32KB memories that
73 are accessed via the TCM A and B port interfaces, for a total of 128KB
74 per processor. In lock-step mode, the processor has access to 256KB of
|
123