From 8e57d9aa275e1ae53522c5d54f5b389dea4bd832 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Thu, 13 Aug 2020 14:16:38 +0000 Subject: [PATCH] --- ConcurrentLinuxSr.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ConcurrentLinuxSr.md b/ConcurrentLinuxSr.md index 4241a6c..464e306 100644 --- a/ConcurrentLinuxSr.md +++ b/ConcurrentLinuxSr.md @@ -1,7 +1,7 @@ # The problems with concurrent burns on Linux Beginning with high version numbers of Linux kernel 2.6 and up to -at least kernel 4.3.0 there is a performance problem when more than +probably kernel 5.6 or 5.7 there is a performance problem when more than one optical drive is used for burning or reading via libburn at the same time. The overall throughput is less than the throughput of the slowest drive when it is used as only one. @@ -31,6 +31,12 @@ and the summary of consequences with remedy proposal: Obviously the deprecated device file family `/dev/sg*` does not have such a lock. +Relief can be expected by a commit of Feb 24, 2020: + + https://github.com/torvalds/linux/commit/51a858817dcdbbdee22cb54b0b2b26eb145ca5b6 + +At that time, the kernel version was in the 5.6-rc era. + # Consequences for libburn ## Using /dev/sg* against all good advise