Home
last modified time | relevance | path

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

/linux-4.4.14/drivers/input/joystick/
Dsidewinder.c215 #define GB(pos,num) sw_get_bits(buf, pos, num, sw->bits) macro
310 if (sw_check(GB(0,64)) || (hat = (GB(6,1) << 3) | GB(60,3)) > 8) in sw_parse()
315 input_report_abs(dev, ABS_X, (GB( 3,3) << 7) | GB(16,7)); in sw_parse()
316 input_report_abs(dev, ABS_Y, (GB( 0,3) << 7) | GB(24,7)); in sw_parse()
317 input_report_abs(dev, ABS_RZ, (GB(35,2) << 7) | GB(40,7)); in sw_parse()
318 input_report_abs(dev, ABS_THROTTLE, (GB(32,3) << 7) | GB(48,7)); in sw_parse()
324 input_report_key(dev, sw_btn[SW_ID_3DP][j], !GB(j+8,1)); in sw_parse()
326 input_report_key(dev, BTN_BASE4, !GB(38,1)); in sw_parse()
327 input_report_key(dev, BTN_BASE5, !GB(37,1)); in sw_parse()
337 if (sw_parity(GB(i*15,15))) in sw_parse()
[all …]
Dgf2k.c158 #define GB(p,n,s) gf2k_get_bits(data, p, n, s) macro
180 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()
183 input_report_abs(dev, gf2k_abs[i], GB(i*9+60,8,0) | GB(i+54,1,9)); in gf2k_read()
185 t = GB(40,4,0); in gf2k_read()
190 t = GB(44,2,0) | GB(32,8,2) | GB(78,2,10); in gf2k_read()
273 if (!(gf2k->id = GB(7,2,0) | GB(3,3,2) | GB(0,3,5))) { in gf2k_connect()
279 if ((gf2k->id != (GB(19,2,0) | GB(15,3,2) | GB(12,3,5))) && in gf2k_connect()
280 (gf2k->id != (GB(31,2,0) | GB(27,3,2) | GB(24,3,5)))) { in gf2k_connect()
/linux-4.4.14/Documentation/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-4.4.14/arch/x86/xen/
DKconfig28 bool "Limit Xen pv-domain memory to 512GB"
32 Limit paravirtualized user domains to 512GB of RAM.
35 pv-domains with more than 512 GB of RAM. This option controls the
36 default setting of the kernel to use only up to 512 GB or more.
Dsetup.c35 #define GB(x) ((uint64_t)(x) * 1024 * 1024 * 1024) macro
552 limit = GB(64) / PAGE_SIZE; in xen_get_pages_limit()
556 limit = GB(512) / PAGE_SIZE; in xen_get_pages_limit()
/linux-4.4.14/Documentation/cgroups/
Dhugetlb.txt38 hugetlb.16GB.limit_in_bytes
39 hugetlb.16GB.max_usage_in_bytes
40 hugetlb.16GB.usage_in_bytes
41 hugetlb.16GB.failcnt
Dmemcg_test.txt127 to be very small rather than GB. Many races found in the test under
129 (Memory behavior under GB and Memory behavior under MB shows very
/linux-4.4.14/Documentation/arm64/
Dmemory.txt11 with the 4KB page configuration, allowing 39-bit (512GB) or 48-bit
28 0000000000000000 0000007fffffffff 512GB user
29 ffffff8000000000 ffffffffffffffff 512GB kernel
94 0000004000000000 0000007fffffffff 256GB kernel objects mapped in HYP
/linux-4.4.14/Documentation/device-mapper/
Dzero.txt29 is an available 10GB partition.
35 10GB of actual storage space available. If more than 10GB of data is written
Ddm-service-time.txt69 and sda has an average throughput 1GB/s and sdb has 4GB/s,
Dthin-provisioning.txt82 The largest size supported is 16GB: If the device is larger,
103 $data_block_size must be between 128 (64KB) and 2097152 (1GB) and a
269 Data block size must be between 64KB (128 sectors) and 1GB
Dcache-policies.txt157 creates a 128GB large mapped device named 'blah' with the
Dcache.txt62 (32KB) and 2097152 (1GB) and a multiple of 64 (32KB).
/linux-4.4.14/Documentation/x86/x86_64/
Dboot-options.txt190 (e.g. because you have < 3 GB memory).
198 you have >3GB memory or told the kernel to us it (iommu=soft))
216 not actually needed (e.g. because < 3 GB memory).
238 allowdac Allow double-address cycle (DAC) mode, i.e. DMA >4GB.
240 two cycles. When off all DMA over >4GB is forced through
242 nodac Forbid DAC mode, i.e. DMA >4GB.
265 4GB. Normally the kernel will make the right choice by itself.
285 Do not use GB pages for kernel direct mappings.
287 Use GB pages for kernel direct mappings.
/linux-4.4.14/Documentation/scsi/
Daha152x.txt136 address the first GB of your disk in the partition table. Therefore
140 (about 8 MB), as soon it sees a disk greater than 1 GB. That results
141 in a maximum of about 8 GB addressable diskspace in the partition table
150 - for disks<1GB: use default translation (C/32/64)
152 - for disks>1GB:
DChangeLog.sym53c8xx_2112 16 registers for up to 4 GB x 16 -> 64 GB.
Ddc395x.txt70 *1 0x02 2 Use DOS compatible mapping for HDs greater than 1GB.
Daic79xx.txt92 - Remove S/G splitting for segments that cross a 4GB boundary.
208 - >4GB memory configurations supported.
DChangeLog.megaraid_sas121 7. Add support for MegaRAID 9360/9380 12GB/s controllers.
Dtmscsim.txt310 *1 0x02 2 Use DOS compatible mapping for HDs greater than 1GB.
Dncr53c8xx.txt261 disks. With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
511 data transferred reaches 1000 GB in order to avoid overflow.
Dsym53c8xx_2.txt233 disks. With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
/linux-4.4.14/Documentation/
Dbus-virt-phys-mapping.txt43 0-2 GB "real memory"
44 2 GB-3 GB "system IO" (inb/out and similar accesses on x86)
45 3 GB-4 GB "IO memory" (shared memory over the IO bus)
49 address 0 actually shows up as address 2 GB for any IO master.
Ddebugging-via-ohci1394.txt25 With most FireWire controllers, memory access is limited to the low 4 GB
31 physical addresses above 4 GB, but this feature is currently not enabled by
108 required for physical DMA above 4 GB (but not utilized by Linux yet).
DManagementStyle214 guy who lost his whole 36GB porn-collection because of your incompetence
Dvfio.txt472 2GB long, uses 4K pages and called "default 32bit window"; the other can
Dkernel-parameters.txt4155 to use only up to 512 GB of RAM. The reason to do so is
/linux-4.4.14/arch/arm/boot/dts/
Dberlin2-sony-nsz-gs7.dts54 reg = <0x00000000 0x40000000>; /* 1 GB */
67 /* Samsung M8G2FA 8GB eMMC */
Ddm8148-evm.dts16 reg = <0x80000000 0x40000000>; /* 1 GB */
Ddm8148-t410.dts16 reg = <0x80000000 0x40000000>; /* 1 GB */
Ddm8168-evm.dts16 reg = <0x80000000 0x40000000 /* 1 GB */
17 0xc0000000 0x40000000>; /* 1 GB */
Dbcm21664-garnet.dts25 reg = <0x80000000 0x40000000>; /* 1 GB */
Dsocfpga_cyclone5_socrates.dts31 reg = <0x0 0x40000000>; /* 1GB */
Dsocfpga_vt.dts32 reg = <0x0 0x40000000>; /* 1 GB */
Dsocfpga_cyclone5_sockit.dts32 reg = <0x0 0x40000000>; /* 1GB */
Dsocfpga_arria5_socdk.dts32 reg = <0x0 0x40000000>; /* 1GB */
Dbcm28155-ap.dts25 reg = <0x80000000 0x40000000>; /* 1 GB */
Dsocfpga_cyclone5_socdk.dts32 reg = <0x0 0x40000000>; /* 1GB */
Dsocfpga_cyclone5_de0_sockit.dts31 reg = <0x0 0x40000000>; /* 1GB */
Dsocfpga_arria10_socdk.dtsi31 reg = <0x0 0x40000000>; /* 1GB */
Dkirkwood-openblocks_a7.dts24 reg = <0x00000000 0x40000000>; /* 1 GB */
Dtegra30-apalis.dtsi5 * Compatible for Revisions 1GB: V1.0A, V1.1A; 1GB IT: V1.1A;
6 * 2GB: V1.0B, V1.0C, V1.0E, V1.1A
Darmada-xp-matrix.dts61 * This board has 4 GB of RAM, but the last 256 MB of
Domap3-n950-n9.dtsi22 reg = <0x80000000 0x40000000>; /* 1 GB */
Darmada-398-db.dts60 reg = <0x00000000 0x80000000>; /* 2 GB */
Darmada-xp-axpwifiap.dts67 reg = <0x00000000 0x00000000 0x00000000 0x40000000>; /* 1GB */
Darmada-375-db.dts63 reg = <0x00000000 0x40000000>; /* 1 GB */
Domap4-duovero.dtsi17 reg = <0x80000000 0x40000000>; /* 1 GB */
Darmada-xp-openblocks-ax3-4.dts62 reg = <0 0x00000000 0 0x40000000>; /* 1 GB soldered on */
Darmada-385-db-ap.dts57 reg = <0x00000000 0x80000000>; /* 2GB */
Domap4-var-som-om44.dtsi17 reg = <0x80000000 0x40000000>; /* 1 GB */
Darmada-xp-db.dts72 reg = <0 0x00000000 0 0x80000000>; /* 2 GB */
Darmada-370-db.dts72 reg = <0x00000000 0x40000000>; /* 1 GB */
Darmada-xp-gp.dts74 * 8 GB of plug-in RAM modules by default.The amount
Darmada-xp-netgear-rn2120.dts61 reg = <0 0x00000000 0 0x80000000>; /* 2GB */
Darmada-388-gp.dts56 reg = <0x00000000 0x80000000>; /* 2 GB */
Darmada-xp-synology-ds414.dts75 reg = <0 0x00000000 0 0x40000000>; /* 1GB */
Domap4-panda-common.dtsi13 reg = <0x80000000 0x40000000>; /* 1 GB */
Domap4-sdp.dts19 reg = <0x80000000 0x40000000>; /* 1 GB */
Drk3288.dtsi182 * haven't found it yet and while devices with 2GB of ram
183 * are not affected, this issue prevents 4GB from booting.
Dsun9i-a80.dtsi108 /* 8GB max. with LPAE */
/linux-4.4.14/Documentation/block/
Dnull_blk.txt35 gb=[Size in GB]: Default: 250GB
Dbiodoc.txt672 - Prevents a clustered segment from crossing a 4GB mem boundary
/linux-4.4.14/arch/arm64/boot/dts/arm/
Dvexpress-v2f-1xv7-ca53x2.dts63 reg = <0 0x80000000 0 0x80000000>; /* 2GB @ 2GB */
/linux-4.4.14/Documentation/filesystems/
Dext2.txt148 larger than 2GB). The translator field is unused under Linux, but is used
317 File size limit: 16GB 256GB 2048GB 2048GB
318 Filesystem size limit: 2047GB 8192GB 16384GB 32768GB
320 There is a 2.4 kernel limit of 2048GB for a single block device, so no
Dtmpfs.txt139 will give you tmpfs instance on /mytmpfs which can allocate 10GB
Df2fs.txt236 which covers 8GB block address range.
247 10 is set, which indicates 10 MB / 1 GB RAM.
Dntfs.txt259 Disk /dev/hda: 81.9 GB, 81964302336 bytes
Dproc.txt823 16GB PIII, which has highmem enabled. You may not have all of these fields.
/linux-4.4.14/arch/arc/boot/dts/
Dnsim_hs.dts22 0x1 0x00000000 0x0 0x40000000>; /* 1 GB highmem */
/linux-4.4.14/tools/perf/Documentation/
Dperf-bench.txt144 Available units are B, KB, MB, GB and TB (case insensitive).
168 Available units are B, KB, MB, GB and TB (case insensitive).
/linux-4.4.14/arch/alpha/kernel/
Dpci.c122 #define GB (1024*MB) macro
186 #undef GB
Dsmc37c93x.c25 #define GB (1024*MB) macro
Dsmc37c669.c23 #define GB (1024*MB) macro
/linux-4.4.14/Documentation/x86/
Dintel_mpx.txt134 1-page structure can require 4 bounds-table pages. An X-GB virtual
135 area needs 4*X GB of virtual space, plus 2GB for the bounds directory.
137 space, we would need to reserve 512TB+2GB, which is larger than the
140 consumes 2GB of virtual *AND* physical memory. IOW, it's completely
/linux-4.4.14/arch/mips/kvm/
D00README.txt14 Guest Usermode virtual memory is limited to 1GB.
/linux-4.4.14/arch/powerpc/boot/dts/
Dkatmai.dts297 /* Inbound 4GB range starting at 0 */
341 /* Inbound 4GB range starting at 0 */
382 /* Inbound 4GB range starting at 0 */
423 /* Inbound 4GB range starting at 0 */
Dredwood.dts257 /* Inbound 2GB range starting at 0 */
298 /* Inbound 2GB range starting at 0 */
339 /* Inbound 2GB range starting at 0 */
Dicon.dts307 /* Inbound 4GB range starting at 0 */
337 /* Inbound 4GB range starting at 0 */
378 /* Inbound 4GB range starting at 0 */
Dxpedite5301.dts142 * Actual part could be ST Micro NAND08GW3B2A (1 GB),
144 * MT29F16G08FAA (2x 1 GB), depending on the build
150 /* U-Boot should fix this up if chip size > 1 GB */
Dxpedite5370.dts140 * Actual part could be ST Micro NAND08GW3B2A (1 GB),
142 * MT29F16G08FAA (2x 1 GB), depending on the build
148 /* U-Boot should fix this up if chip size > 1 GB */
Dxpedite5330.dts178 * Actual part could be ST Micro NAND08GW3B2A (1 GB),
180 * MT29F16G08FAA (2x 1 GB), depending on the build
186 /* U-Boot should fix this up if chip size > 1 GB */
Dxcalibur1501.dts142 * Actual part could be ST Micro NAND08GW3B2A (1 GB),
144 * MT29F16G08FAA (2x 1 GB), depending on the build
150 /* U-Boot should fix this up if chip size > 1 GB */
Dsequoia.dts391 * PCI 1 Memory 1 8000 0000 1 BFFF FFFF 1GB
399 /* Inbound 2GB range starting at 0 */
Dmakalu.dts290 /* Inbound 2GB range starting at 0 */
331 /* Inbound 2GB range starting at 0 */
Dcanyonlands.dts444 /* Inbound 2GB range starting at 0 */
475 /* Inbound 2GB range starting at 0 */
517 /* Inbound 2GB range starting at 0 */
Dglacier.dts481 /* Inbound 2GB range starting at 0 */
512 /* Inbound 2GB range starting at 0 */
554 /* Inbound 2GB range starting at 0 */
Dep405.dts215 /* Inbound 2GB range starting at 0 */
Dkilauea.dts344 /* Inbound 2GB range starting at 0 */
385 /* Inbound 2GB range starting at 0 */
Dwalnut.dts222 /* Inbound 2GB range starting at 0 */
Dhotfoot.dts276 /* Inbound 2GB range starting at 0 */
Dsam440ep.dts285 /* Inbound 2GB range starting at 0 */
Dhaleakala.dts259 /* Inbound 2GB range starting at 0 */
Dc2k.dts49 reg = <0x00000000 0x40000000>; /* 1GB */
Dbamboo.dts276 /* Inbound 2GB range starting at 0 */
Debony.dts313 /* Inbound 2GB range starting at 0 */
Dyosemite.dts318 /* Inbound 2GB range starting at 0 */
Drainier.dts337 /* Inbound 2GB range starting at 0 */
Dbluestone.dts363 /* Inbound 2GB range starting at 0 */
Dtaishan.dts404 /* Inbound 2GB range starting at 0 */
/linux-4.4.14/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt74 * Is limited to 4GB in size.
79 don't touch it from Linux; it's usually set to forward a 2GB
88 to be assigned to PEs on a segment granularity. For a 2GB window,
89 the segment granularity is 2GB/256 = 8MB.
121 that has been assigned by FW for the PHB (about 64GB, ignore the space
/linux-4.4.14/arch/s390/kernel/
Dhead64.S70 .Lscan2g:.quad 0x80000000 + 0x20000 - 8 # 2GB + 128K - 8
/linux-4.4.14/drivers/char/agp/
Dhp-agp.c33 #define HP_ZX1_IOVA_BASE GB(1UL)
34 #define HP_ZX1_IOVA_SIZE GB(1UL)
Dagp.h160 #define GB(x) (MB (KB (x))) macro
/linux-4.4.14/arch/arm/mm/
Dproc-arm740.S74 mov r0, #0x0000003F @ base = 0, size = 4GB
Dproc-arm940.S295 mov r0, #0x0000003F @ base = 0, size = 4GB
Dproc-arm946.S342 mov r0, #0x0000003F @ base = 0, size = 4GB
DKconfig634 4GB limit. The resulting kernel image will not run on
/linux-4.4.14/arch/x86/mm/
Dmpx.c727 unsigned long long GB = (1ULL << 30); in bd_entry_virt_space() local
734 return (4ULL * GB) / MPX_BD_NR_ENTRIES_32; in bd_entry_virt_space()
/linux-4.4.14/Documentation/ide/
Dide-tape.txt38 Testing was done with a 2 GB CONNER CTMA 4000 IDE ATAPI Streaming Tape Drive.
DChangeLog.ide-tape.1995-2002157 * Ver 1.13 Jan 2 98 Add "speed == 0" work-around for HP COLORADO 5GB
/linux-4.4.14/Documentation/frv/
Dmmu-layout.txt63 00004000-BFFFFFFF various TLB,xAMR1 D-N-??V 3GB Userspace
126 up to 3GB of SDRAM (possibly 3.25GB) to be made available. By using CONFIG_HIGHMEM, the kernel can
/linux-4.4.14/Documentation/virtual/kvm/devices/
Dvm.txt39 2048 MB, 4096 GB, 8192 TB respectively, as this limit is governed by
/linux-4.4.14/Documentation/arm/
Dmemory.txt10 The ARM CPU is capable of addressing a maximum of 4GB virtual memory
/linux-4.4.14/Documentation/mic/
Dscif_overview.txt37 Throughput (GB/sec)
/linux-4.4.14/arch/arm/mach-realview/
DKconfig126 offset. On the PBX board, disabling this option allows 1GB of
/linux-4.4.14/arch/powerpc/mm/
Dhash_utils_64.c76 #define GB (1024L*MB) macro
434 if (block_size != (16 * GB)) in htab_dt_scan_hugepage_blocks()
439 if (phys_addr + (16 * GB) <= memblock_end_of_DRAM()) { in htab_dt_scan_hugepage_blocks()
/linux-4.4.14/Documentation/vm/
Dpage_owner.txt59 more accurately. On 2GB memory x86-64 VM box, 13343 early allocated pages
Dfrontswap.txt143 4K pagesize, this is 1MB per 32GB swap.
Dunevictable-lru.txt59 To illustrate this with an example, a non-NUMA x86_64 platform with 128GB of
/linux-4.4.14/Documentation/networking/
Dnf_conntrack-sysctl.txt15 with more than 4GB of memory it will be 65536 buckets.
/linux-4.4.14/arch/arm/kernel/
Dhead-nommu.S225 mov r6, #MPU_RSR_ALL_MEM @ 4GB region, enabled
/linux-4.4.14/arch/ia64/sn/pci/
Dtioce_provider.c186 #define GB(x) ((u64)(x) << 30) macro
318 pagesize = GB(16); in tioce_alloc_map()
/linux-4.4.14/tools/lguest/
Dlguest.txt35 "High Memory Support" = off/4GB
/linux-4.4.14/arch/x86/
DKconfig793 limitations, on systems with more than 3 GB. This is usually needed
800 there's more than 3 GB of memory and the system contains a
811 systems. Needed to run systems with more than 3GB of memory
841 with more than 3 GB of memory.
1206 choice and suitable for most users). This will result in a "3GB/1GB"
1207 split: 3GB are mapped so that each process sees a 3GB virtual memory
1208 space and the remaining part of the 4GB virtual memory space is used
1213 answer "4GB" here.
1215 If more than 4 Gigabytes is used then answer "64GB" here. This
1219 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
[all …]
DKconfig.debug193 Force the IOMMU to on even when you have less than 4GB of
/linux-4.4.14/Documentation/kdump/
Dkdump.txt383 systems with more than 4GB memory. On i386, kexec automatically checks if
384 the physical RAM size exceeds the 4 GB limit and if not, uses ELF32.
465 On systems with a maximum of 4GB of memory, you can generate
/linux-4.4.14/Documentation/blockdev/
Dparide.txt47 Hewlett-Packard 5GB and 8GB tape drives
119 Hewlett-Packard 5GB Tape pt epat
DREADME.DAC960241 large disk arrays it is advisable to enable the 8GB BIOS Geometry (255/63)
242 rather than accepting the default 2GB BIOS Geometry (128/32); failing to so do
244 will make it impossible for FDISK to be used properly. The 8GB BIOS Geometry
415 configuration comprises 6 1GB Quantum Atlas I disk drives on two channels of a
587 configuration comprises 6 1GB Quantum Atlas I disk drives on two channels of a
/linux-4.4.14/drivers/block/
DKconfig75 with up to 1 GB of data. This drive will also read standard CD ROM
541 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
545 storage device: Flash Adapter 900GB Full Height.
/linux-4.4.14/Documentation/s390/
DDebugging390.txt199 0xFFFFFFFF 4GB Himem *****************
205 (typically 0xC0000000 3GB ) ***************** * *
227 Himem=0xFFFFFFFF-0xC0000000=1GB & this is all the RAM these machines
229 They can lower User Himem to 2GB or lower & thus be
230 able to use 2GB of RAM however this shrinks the maximum size
231 of User Space from 3GB to 2GB they have a no win limit of 4GB unless
236 For backward compatibility we are only allowed use 31 bits (2GB)
240 This means we can support 2GB of non Extended RAM on s/390, & more
251 Himem 0x7fffffff 2GB on s/390 ***************** ****************
/linux-4.4.14/arch/x86/kernel/
Dearly-quirks.c246 #define GB(x) (MB (KB (x))) macro
/linux-4.4.14/Documentation/virtual/kvm/
Dmmu.txt52 pages, pae, pse, pse36, cr0.wp, and 1GB pages. Work is in progress to support
140 by role.level (2MB for first level, 1GB for second level, 0.5TB for third
153 quadrant maps 1GB virtual address space.
Dapi.txt980 physical address space. The region must be within the first 4GB of the
1100 physical address space. The region must be within the first 4GB of the
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dmvebu-pci.txt54 4 GB of the physical address space, and do not translate into a valid CPU
/linux-4.4.14/arch/parisc/
DKconfig201 At the moment, only people willing to use more than 2GB of RAM,
/linux-4.4.14/fs/squashfs/
DKconfig12 and files (larger than 4GB), full uid/gid information, hard links and
/linux-4.4.14/arch/arm/mach-ixp4xx/
DKconfig214 memory space. This currently allows for up to 1 GB (0x10000000
/linux-4.4.14/arch/frv/
DKconfig91 The arch is, however, capable of supporting up to 3GB of SDRAM.
/linux-4.4.14/arch/cris/arch-v10/
DREADME.mm93 The MMU can map all 4 GB in user mode, but doing that would mean that a
/linux-4.4.14/arch/powerpc/platforms/
DKconfig.cputype227 If you have more than 3.5GB of RAM or so, you also need to enable
/linux-4.4.14/arch/arm64/boot/dts/freescale/
Dfsl-ls2080a.dtsi125 /* DRAM space - 1, size : 2 GB DRAM */
/linux-4.4.14/arch/tile/
DKconfig260 physical memory into the top 1 GB of virtual memory space.
/linux-4.4.14/drivers/scsi/
DKconfig1062 of 4 GB each. This limits the total addressable range to 64 GB.
1064 Most machines with less than 4GB of memory should use a setting
1065 of 0 for best performance. If your machine has 4GB of memory
1069 x 4GB segments limitation) can be used on systems that require
/linux-4.4.14/drivers/block/paride/
DKconfig66 parallel port version of the HP 5GB drive.
/linux-4.4.14/Documentation/fb/
Dmatroxfb.txt337 (for 32bpp it is about 3GB of data (exactly 3000 MB); for 8x16 font in
/linux-4.4.14/Documentation/power/
Dswsusp.txt153 kernels from swsusp.sourceforge.net. It includes support for SMP, 4GB
/linux-4.4.14/arch/alpha/
DKconfig634 allocations. This equates to about 8GB.
/linux-4.4.14/mm/
DKconfig288 # have more than 4GB of memory, but we don't currently use the IOTLB to present
/linux-4.4.14/Documentation/filesystems/cifs/
DREADME55 the modules directory e.g. /lib/modules/2.4.10-4GB/kernel/fs/cifs/cifs.o).
/linux-4.4.14/drivers/eisa/
Deisa.ids1045 ISAD900 "NEC Multisync Graphics Board GB-1"
/linux-4.4.14/lib/
DKconfig.debug1722 firescope and access all memory below 4GB using fireproxy from gdb.
/linux-4.4.14/arch/mips/
DKconfig1690 of lowmem (up to 3GB). If unsure, say 'N' here.
/linux-4.4.14/
DMAINTAINERS4392 FLASH ADAPTER DRIVER (IBM Flash Adapter 900GB Full Height PCI Flash Card)