Linux Kernel and Graphics Leftovers


-
Preserving the mobility of ZONE_MOVABLE
Memory fragmentation has long been a problem for Linux systems, to the point that, for years, finding even two physically contiguous pages was an uncertain affair. That said, the situation has improved considerably in the last decade or so thanks to a number of changes implemented by the memory-management developers. One of those changes is the creation of "movable" memory zones where pages can be relocated if need be. All that work is for nothing, though, if somebody comes along and pins down a page in one of these movable zones. This patch set from Pavel Tatashin seeks to prevent that from happening, but may risk creating problems elsewhere.
The Linux kernel allocates and frees pages of memory at a high rate; at any given time, there is no real way to predict which pages will be free, and which will be in use. Those in-use pages have an annoying tendency to be spread out across physical memory, making it hard to find a range of free, physically contiguous pages. The increasing use of huge pages, though, has increased the demand for contiguous regions — regions that will not be available if the kernel does not make an active effort to create them.Contemporary systems can also face a related problem: hotpluggable memory. While there are machines with memory that can be physically yanked out of the box, hotplugging is more commonly used in the context of virtualization. Virtual machines experiencing memory thrashing can have more memory "plugged" into them by the hypervisor, while those that are not fully using the memory they have can be made to give some back to the system. Unplugging memory can be seen as a special case of the "large, physically contiguous region" problem — the whole range of memory must be made to be free so it can be unplugged without data loss — with the added constraint that the region must be located at a specific address. It is fair to say that this rarely happens by chance.
-
Avoiding blocking file-name lookups
As a general rule, when one attempts to open a file with a system call like openat2(), the expectation is that the call will not return until the job is done. But there are times where the desire to open the file is conditional on being able to open it immediately, without blocking. Linux has never supported that mode well, but that may be about to change with this patch set from Jens Axboe.
Opening a file can be a complex operation. Simply resolving the name of the file can require traversing a series of directories that may be located on different filesystems; each step may also require performing I/O and taking locks to serialize changes that might otherwise create unwelcome surprises. Once the file has been found, there may be more I/O required to perform the open itself. Each of these steps has the potential to block the opening task for an unknown period of time.Axboe's patch set creates a new internal flag called LOOKUP_CACHED, which is then made available to callers of openat2() as RESOLVE_CACHED. This flag requests the kernel to only carry the open to completion if that can be done using only data that is cached in memory — without performing I/O, in other words. If it becomes clear during the attempt that I/O would be required, the openat2() call will fail with an EAGAIN error. The caller can then retry the operation without RESOLVE_CACHED — in a setting where blocking is tolerable — to successfully open the file.
-
Best practices for adapting Phoronix Test Suite to benchmark Linux performance
The Phoronix Test Suite (PTS) is a comprehensive testing and benchmarking platform, which is widely used to help assess the performance of Linux systems. We have been using PTS to understand and track the performance of Oracle Linux (OL) over time, particularly while running on cloud instances, such as those provided by Oracle Cloud Infrastructure (OCI). Further, we also measure PTS performance on cloud instances running other versions of Linux, such as CentOS and Ubuntu.
A key requirement of using workloads to track performance is result repeatability. If run-to-run variability is too high, then the workload results can not be used to accurately determine changes in performance. While using PTS, we started with the default installation and execution (parameter) settings; however, we noticed that, in several cases, results were highly variable. Detailed analysis helped us identify the reasons for this behavior, showing us the need to modify how we run certain workloads so that more consistent results are achieved, allowing us to detect smaller changes as statistically significant.
-
Mike Blumenkrantz: Mo Cards Mo Problems
Thanks once again to my generous sponsors at Valve, as well as a patch from a GLX guru with the very accurate commit log “I hate everything.”, I put in a little time today and came up with this
-
Zink OpenGL-On-Vulkan Now Works Atop NVIDIA's Linux Driver - Phoronix
Zink as the generic OpenGL implementation built atop the Vulkan API while leveraging Mesa's Gallium3D can now work atop NVIDIA's proprietary graphics driver.
To date the Zink code within Mesa has been tested against Intel's ANV and AMD Radeon RADV Vulkan drivers. But now thanks to Mike Blumenkrantz, who is being funded by Valve for this graphics driver work, it can now run on the NVIDIA proprietary Vulkan driver.
-

- Login or register to post comments
Printer-friendly version- 2095 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

OpenGL on top of Vulkan with Zink to work with NVIDIA
OpenGL on top of Vulkan with Zink to work with NVIDIA drivers on Linux