Hello everyone,
I’d like to bring up an important question regarding the future of the TVS-871 and its compatibility with QTS 6.
My TVS-871 is currently running QTS 5.2.11 with QNAP’s Linux 5.10.60 kernel. Although this is an older platform, it remains a capable 8-bay NAS with an Intel x86-64 architecture, PCIe expansion capabilities and 16 GB of RAM.
What concerns me is the possibility that this hardware generation could be excluded from QTS 6 without taking into account just how much the Linux kernel has evolved between 5.10 and 6.6.
I’ve been looking through the upstream Linux kernel release notes, and there are quite a few changes that I believe would be genuinely worthwhile on this platform. I am not talking about cosmetic improvements or features that only benefit the latest processors. Several developments directly concern CPU scheduling, memory management, software RAID, ext4, block I/O and networking.
One of the most interesting changes is the introduction of EEVDF in Linux 6.6, replacing the previous CFS scheduling algorithm. This changes how CPU execution time is allocated between competing processes, with the objective of improving scheduling fairness and responsiveness, particularly for latency-sensitive tasks. On a NAS running SMB, background indexing, RAID operations, backup services and several applications simultaneously, this is certainly worth evaluating.
Memory management has also evolved considerably. Linux 6.1 introduced Multi-Gen LRU (MGLRU), an alternative page-reclaim algorithm designed to make better decisions about which memory pages should remain in RAM and which should be reclaimed. Unlike the traditional LRU approach, it uses multiple generations of page access information to improve working-set identification. This is particularly interesting for a system with 16 GB of RAM handling filesystem caching and several concurrent services. I would like QNAP to consider enabling and benchmarking this mechanism where appropriate.
There are also significant developments in the I/O infrastructure. Linux 6.6 includes an improvement to asynchronous direct I/O through io_uring, with reported throughput and latency improvements of up to 37% in certain low-queue-depth workloads. Obviously, this is not a guaranteed 37% improvement in NAS transfers, but it demonstrates the potential of the newer I/O implementation. It would be interesting to know whether QNAP’s storage services could take advantage of these developments.
What particularly caught my attention is that the Linux 6.6 release notes explicitly mention changes to the software RAID subsystem itself. For example, md/raid1 received an improvement designed to avoid lock contention caused by wake_up(). There are also changes in block-layer request handling and I/O accounting. These are not theoretical benefits for an unrelated platform: the TVS-871 uses Linux software RAID and its storage architecture is directly dependent on these components.
The filesystem layer has also received relevant improvements. Linux 6.6 includes an optimisation for ext4 delayed-allocation append writes (ext4 delalloc append write). In addition, the iomap infrastructure has received changes to improve asynchronous direct I/O by avoiding unnecessary workqueue transitions in certain paths, as well as reducing write amplification in specific block-size/page-size scenarios. These changes deserve particular attention on an eight-disk storage system handling large files and sustained write workloads.
Linux 6.1 also introduced significant improvements to BPF, including new data structures, memory allocation mechanisms and additional helpers. Linux 6.3 continued this development with TCX, an improved attachment API for traffic-control BPF programs, and further networking capabilities. These developments could provide better monitoring, filtering and network management possibilities within future QTS versions, provided QNAP chooses to integrate them.
Networking itself has also progressed. Linux 6.3 introduced IPv4 BIG TCP, extending TSO/GRO packet handling beyond the traditional 64 KB limit. Depending on the network driver, hardware offload capabilities and interface configuration, this can reduce packet-processing overhead in high-throughput environments. I would particularly like QNAP to evaluate these improvements for users with PCIe 10 GbE expansion cards and other high-speed interfaces.
Security is another important consideration. Linux 6.1 introduced KCFI (Kernel Control Flow Integrity), including support for x86-64, providing a mechanism to detect certain forms of invalid control-flow transfers. Linux 6.6 also introduced support for Intel CET shadow stacks in userspace, although this particular hardware protection requires compatible processors and would not be available on the Haswell generation. This illustrates why I would prefer a proper evaluation of each security mechanism rather than a generic statement about kernel compatibility.
There are also other developments worth considering: more configurable unbound workqueues in 6.6, improved PSI resource-pressure reporting in 6.1, additional memory-management optimisations, continued development of the device-mapper and ATA subsystems, and numerous driver updates across the intervening releases.
Of course, not every new kernel feature is relevant to the TVS-871. Some require newer processor instructions, specific hardware, particular kernel configuration options or userspace integration. My point is that there are enough directly relevant developments to justify an actual engineering assessment.
The TVS-871 uses an established Intel x86-64 platform, with the Intel B85 chipset, Intel SATA/AHCI infrastructure and Intel I210 Ethernet controllers. These rely on standard Linux subsystems and drivers such as ahci, libata and igb. I would like QNAP to investigate whether these components, together with its proprietary kernel modules and hardware-management interfaces, can be maintained on a Linux 6.6 base.
I would also like to see improvements to the native hardware monitoring capabilities, particularly the ability to expose PCIe expansion-card temperatures through QTS rather than relying on third-party scripts or manual modifications.
I fully understand that moving from 5.10 to 6.6 is not simply a matter of replacing the kernel image. QNAP would need to rebuild and validate its proprietary modules, storage management stack, fan-control mechanisms, boot environment and other platform-specific components. Existing RAID metadata, storage pools, Device Mapper volumes, ext4 filesystems, ACLs and extended attributes would also need to remain fully compatible.
However, I don’t believe these engineering requirements should automatically result in the exclusion of an otherwise functional x86-64 platform.
I would much rather see QNAP offer a dedicated experimental firmware build for the TVS-871 than see this generation permanently limited to the 5.2 branch without any technical evaluation.
I would particularly appreciate an answer from the development team on whether the TVS-X71 hardware platform has actually been assessed against Linux 6.6, and whether the main obstacles are related to hardware compatibility, proprietary QNAP kernel modules, boot firmware or simply product-support policy.
There are several years of Linux kernel development between 5.10 and 6.6. The TVS-871 should have the opportunity to benefit from these improvements rather than being excluded solely because of its age.
I hope other TVS-X71 owners will support this request and that QNAP will consider investigating the feasibility of bringing QTS 6 to this platform.
Thank you. ![]()