Home
last modified time | relevance | path

Searched refs:GB (Results 1 – 25 of 215) sorted by relevance

123456789

/linux-5.19.10/Documentation/translations/zh_CN/riscv/ !
Dvm-layout.rst43 0000000000000000 | 0 | 0000003fffffffff | 256 GB | 用户空间虚拟内存,每个内存管理器不同
46 0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... 巨大的、几乎64位宽的直到内核映射的-256GB地方
54 ffffffc6fee00000 | -228 GB | ffffffc6feffffff | 2 MB | fixmap
55 ffffffc6ff000000 | -228 GB | ffffffc6ffffffff | 16 MB | PCI io
56 ffffffc700000000 | -228 GB | ffffffc7ffffffff | 4 GB | vmemmap
57 ffffffc800000000 | -224 GB | ffffffd7ffffffff | 64 GB | vmalloc/ioremap space
58 ffffffd800000000 | -160 GB | fffffff6ffffffff | 124 GB | 直接映射所有物理内存
59 fffffff700000000 | -36 GB | fffffffeffffffff | 32 GB | kasan
65 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules, BPF
66 ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel
/linux-5.19.10/Documentation/riscv/ !
Dvm-layout.rst39 …0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different …
42 …0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
43 … | | | | virtual memory addresses up to the -256 GB
50 ffffffc6fee00000 | -228 GB | ffffffc6feffffff | 2 MB | fixmap
51 ffffffc6ff000000 | -228 GB | ffffffc6ffffffff | 16 MB | PCI io
52 ffffffc700000000 | -228 GB | ffffffc7ffffffff | 4 GB | vmemmap
53 ffffffc800000000 | -224 GB | ffffffd7ffffffff | 64 GB | vmalloc/ioremap space
54 … ffffffd800000000 | -160 GB | fffffff6ffffffff | 124 GB | direct mapping of all physical memory
55 fffffff700000000 | -36 GB | fffffffeffffffff | 32 GB | kasan
61 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules, BPF
[all …]
/linux-5.19.10/drivers/input/joystick/ !
Dsidewinder.c199 #define GB(pos,num) sw_get_bits(buf, pos, num, sw->bits) macro
294 if (sw_check(GB(0,64)) || (hat = (GB(6,1) << 3) | GB(60,3)) > 8) in sw_parse()
299 input_report_abs(dev, ABS_X, (GB( 3,3) << 7) | GB(16,7)); in sw_parse()
300 input_report_abs(dev, ABS_Y, (GB( 0,3) << 7) | GB(24,7)); in sw_parse()
301 input_report_abs(dev, ABS_RZ, (GB(35,2) << 7) | GB(40,7)); in sw_parse()
302 input_report_abs(dev, ABS_THROTTLE, (GB(32,3) << 7) | GB(48,7)); in sw_parse()
308 input_report_key(dev, sw_btn[SW_ID_3DP][j], !GB(j+8,1)); in sw_parse()
310 input_report_key(dev, BTN_BASE4, !GB(38,1)); in sw_parse()
311 input_report_key(dev, BTN_BASE5, !GB(37,1)); in sw_parse()
321 if (sw_parity(GB(i*15,15))) in sw_parse()
[all …]
Dgf2k.c142 #define GB(p,n,s) gf2k_get_bits(data, p, n, s) macro
164 input_report_abs(dev, gf2k_abs[i], GB(i<<3,8,0) | GB(i+46,1,8) | GB(i+50,1,9)); in gf2k_read()
167 input_report_abs(dev, gf2k_abs[i], GB(i*9+60,8,0) | GB(i+54,1,9)); in gf2k_read()
169 t = GB(40,4,0); in gf2k_read()
174 t = GB(44,2,0) | GB(32,8,2) | GB(78,2,10); in gf2k_read()
257 if (!(gf2k->id = GB(7,2,0) | GB(3,3,2) | GB(0,3,5))) { in gf2k_connect()
263 if ((gf2k->id != (GB(19,2,0) | GB(15,3,2) | GB(12,3,5))) && in gf2k_connect()
264 (gf2k->id != (GB(31,2,0) | GB(27,3,2) | GB(24,3,5)))) { in gf2k_connect()
/linux-5.19.10/Documentation/x86/x86_64/ !
Dmm.rst20 from TB to GB and then MB/KB.
62 ffffff8000000000 | -512 GB | ffffffeeffffffff | 444 GB | ... unused hole
63 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
64 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | ... unused hole
65 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
121 ffffff8000000000 | -512 GB | ffffffeeffffffff | 444 GB | ... unused hole
122 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
123 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | ... unused hole
124 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
/linux-5.19.10/Documentation/translations/zh_CN/arm64/ !
Dmemory.txt36 分别都有 39-bit (512GB) 或 48-bit (256TB) 的虚拟地址空间。
49 0000000000000000 0000007fffffffff 512GB 用户空间
50 ffffff8000000000 ffffffffffffffff 512GB 内核空间
114 0000004000000000 0000007fffffffff 256GB 在 HYP 中映射的内核对象
/linux-5.19.10/Documentation/translations/zh_TW/arm64/ !
Dmemory.txt40 分別都有 39-bit (512GB) 或 48-bit (256TB) 的虛擬地址空間。
53 0000000000000000 0000007fffffffff 512GB 用戶空間
54 ffffff8000000000 ffffffffffffffff 512GB 內核空間
118 0000004000000000 0000007fffffffff 256GB 在 HYP 中映射的內核對象
/linux-5.19.10/Documentation/admin-guide/cgroup-v1/ !
Dhugetlb.rst37 hugetlb.1GB.limit_in_bytes
38 hugetlb.1GB.max_usage_in_bytes
39 hugetlb.1GB.numa_stat
40 hugetlb.1GB.usage_in_bytes
41 hugetlb.1GB.failcnt
42 hugetlb.1GB.rsvd.limit_in_bytes
43 hugetlb.1GB.rsvd.max_usage_in_bytes
44 hugetlb.1GB.rsvd.usage_in_bytes
45 hugetlb.1GB.rsvd.failcnt
/linux-5.19.10/tools/perf/Documentation/ !
Dperf-iostat.txt57 375083606016 bytes (375 GB, 349 GiB) copied, 215.974 s, 1.7 GB/s
76 375083606016 bytes (375 GB, 349 GiB) copied, 197.08 s, 1.9 GB/s
/linux-5.19.10/arch/x86/xen/ !
DKconfig31 bool "Limit Xen pv-domain memory to 512GB"
35 Limit paravirtualized user domains to 512GB of RAM.
38 pv-domains with more than 512 GB of RAM. This option controls the
39 default setting of the kernel to use only up to 512 GB or more.
/linux-5.19.10/arch/arm/boot/dts/ !
Dberlin2-sony-nsz-gs7.dts23 reg = <0x00000000 0x40000000>; /* 1 GB */
36 /* Samsung M8G2FA 8GB eMMC */
Dimx6ull-colibri-emmc-aster.dts12 model = "Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Aster";
Dimx6ull-colibri-emmc-iris.dts12 model = "Toradex Colibri iMX6ULL 1GB (eMMC) on Colibri Iris";
/linux-5.19.10/arch/arm64/boot/dts/ti/ !
Dk3-am6548-iot2050-advanced.dts10 * 2 GB RAM, 16 GB eMMC, USB-serial converter on connector X30
Dk3-am6548-iot2050-advanced-pg2.dts10 * 2 GB RAM, 16 GB eMMC, USB-serial converter on connector X30
/linux-5.19.10/Documentation/admin-guide/device-mapper/ !
Dzero.rst30 is an available 10GB partition::
36 10GB of actual storage space available. If more than 10GB of data is written
/linux-5.19.10/Documentation/vm/ !
Dvmemmap_dedup.rst16 details. On the x86-64 architecture, HugeTLB pages of size 2MB and 1GB are
18 consists of 512 base pages and a 1GB HugeTLB page consists of 4096 base pages.
38 | x86-64 | 4KB | 2MB | 1GB | | |
40 | | 4KB | 64KB | 2MB | 32MB | 1GB |
42 | arm64 | 16KB | 2MB | 32MB | 1GB | |
44 | | 64KB | 2MB | 512MB | 16GB | |
92 E.g.: A 2MB HugeTLB page on x86_64 consists in 8 page frames while 1GB
/linux-5.19.10/arch/mips/boot/dts/brcm/ !
Dbcm97435svmb.dts134 /* 1GB Memc0, 1GB Memc1 */
Dbcm97425svmb.dts158 /* 1GB Memc0, 1GB Memc1 */
/linux-5.19.10/arch/arc/boot/dts/ !
Dhaps_hs.dts19 reg = <0x0 0x80000000 0x0 0x40000000 /* 1 GB low mem */
20 0x1 0x00000000 0x0 0x40000000>; /* 1 GB highmem */
/linux-5.19.10/Documentation/devicetree/bindings/pci/ !
Dv3-v360epc-pci.txt23 64MB, 128MB, 256MB, 512MB, 1GB or 2GB in size. The memory should be marked
52 0x80000000 0 0x40000000>; /* 1GB @ LB 80000000 */
/linux-5.19.10/Documentation/scsi/ !
Daha152x.rst155 address the first GB of your disk in the partition table. Therefore
159 (about 8 MB), as soon it sees a disk greater than 1 GB. That results
160 in a maximum of about 8 GB addressable diskspace in the partition table
169 - for disks<1GB: use default translation (C/32/64)
171 - for disks>1GB:
/linux-5.19.10/Documentation/core-api/ !
Dbus-virt-phys-mapping.rst53 0-2 GB "real memory"
54 2 GB-3 GB "system IO" (inb/out and similar accesses on x86)
55 3 GB-4 GB "IO memory" (shared memory over the IO bus)
59 address 0 actually shows up as address 2 GB for any IO master.
/linux-5.19.10/tools/testing/selftests/cgroup/ !
Dmemcg_protection.m19 % example from testcase (values in GB)
27 % Minimal reclaim amount (GB)
/linux-5.19.10/arch/arm64/boot/dts/arm/ !
Dvexpress-v2f-1xv7-ca53x2.dts65 reg = <0 0x80000000 0 0x80000000>; /* 2GB @ 2GB */

123456789