parent
ae2b697692
commit
8e57d9aa27
@ -1,7 +1,7 @@
|
|||||||
# The problems with concurrent burns on Linux
|
# The problems with concurrent burns on Linux
|
||||||
|
|
||||||
Beginning with high version numbers of Linux kernel 2.6 and up to
|
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.
|
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
|
The overall throughput is less than the throughput of the slowest drive
|
||||||
when it is used as only one.
|
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
|
Obviously the deprecated device file family `/dev/sg*` does not have such
|
||||||
a lock.
|
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
|
# Consequences for libburn
|
||||||
|
|
||||||
## Using /dev/sg* against all good advise
|
## Using /dev/sg* against all good advise
|
||||||
|
Loading…
Reference in New Issue
Block a user