>> We lose some ram on aarch64 due to cma allocation, its something that is >> actively being looked at. Anaconda also needs a fair amount of ram during >> the network install to copy files. Once the install is complete, you should >> be able to reduce the ram to 2048. > > 2G not being enough is pretty excessive. I never had such problems on > x86. Only recently (a year ago or so) I started using 2G for guests, 1G > used to be enough even for network installs. Completely agree, generally if you're doing a anaconda based install you need at least 768Mb due to various combinations of installer memory usage and selinux applying policies. > I suspect a big factor here is CONFIG_ARM64_64K_PAGES=y. Raspberry pi > 3, with standard fedora kernel (64k pages), minimal install (@core), > booted to the shell prompt. "free" reports ~122MB of memory as used. > Same with a self-compiled kernel (4k pages), I get ~44MB of used memory. > That is almost factor three! That is almost the complete factor. It's in fact a combination of 64K pages and CMA. The two together mean that the minimum CMA allocated is 512Mb of RAM. It's a known problem and one we're looking at different ways/options to resolve and working with upstream to do so and reconsidering 64K pages in Fedora. We've traditionally gone that route due to large enterprise systems and to be in sync with downstreams like RHELSA and CentOS in that regard. Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
