libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

New command -scsi_dev_family, new -as cdrecord option drive_scsi_dev_family=

Browse Source
This commit is contained in:
Thomas Schmitt
2016-03-18 13:55:09 +00:00
parent e51a00f000
commit 3664cab771
19 changed files with 337 additions and 119 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
xorriso/xorriso.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.4.3, Feb 05, 2016"
.TH XORRISO 1 "Version 1.4.3, Mar 18, 2016"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -304,6 +304,12 @@ the path of their block device or of their generic character device. E.g.
.br
\-dev /dev/sg2
.br
By default xorriso will try to map the given address to /dev/hd* and /dev/sr*.
The command \-scsi_dev_family can redirect the mapping from sr to scd or sg.
The latter does not suffer from the concurrency problems which plague /dev/sr
of Linux kernels since version 3. But it does not yield the same addresses
which are used by mount(8) or by open(2) for read(2).
.br
On FreeBSD the device files have names like
.br
\-dev /dev/cd0
@ -678,6 +684,26 @@ apply. See above paragraph "Libburn drives".
An empty address string "" gives up the current output drive
without acquiring a new one. No writing is possible without an output drive.
.TP
\fB\-scsi_dev_family\fR "default"|"sr"|"scd"|"sg"
GNU/Linux specific:
.br
By default, xorriso tries to map Linux drive addresses to /dev/sr* before
they get opened for operating the drive. This coordinates well with
other use cases of optical drives, like mount(8). But since year 2010
all /dev/sr* share a global lock which allows only one drive to process
an SCSI command while all others have to wait for its completion.
This yields awful throughput if more than one drive is writing or reading
simultaneously.
The global lock is not applied to device files /dev/sg* and also not if
the xorriso drive address is prepended by "stdio:".
.br
So for simultaneous burn runs on modern GNU/Linux it is advisable to perform
\-scsi_dev_family "sg" before any \-dev, \-indev, or \-outdev. The drive addresses
may then well be given as /dev/sr* but will nevertheless get used as /dev/sg*.
.br
If you decide so, consider to put the command into a global startup file like
/etc/opt/xorriso/rc.
.TP
\fB\-grow_blindly\fR "off"|predicted_nwa
If predicted_nwa is a non\-negative number then perform blind growing rather
than modifying if \-indev and \-outdev are set to different drives.
@ -2940,9 +2966,11 @@ reaches a given low percentage value.
.br
This can ease the load on operating system and drive controller and thus help
with achieving better input bandwidth if disk and burner are not on independent
controllers (like hda and hdb). It may also help with simultaneous burns on
different burners with Linux kernels like 3.16. On the other hand it increases
the risk of buffer underflow and thus reduced write speed.
controllers (like hda and hdb). It may also help with throughput problems of
simultaneous burns on different burners with Linux kernels like 3.16, if one
has reason not to fix the problem by \-scsi_dev_family "sg".
On the other hand it increases the risk of buffer underflow and thus
reduced write speed.
.br
Some burners are not suitable because they
report buffer fill with granularity too coarse in size or time,