New command -scsi_dev_family, new -as cdrecord option drive_scsi_dev_family=
This commit is contained in:
@ -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 XORRECORD 1 "Version 1.4.3, Feb 05, 2016"
|
||||
.TH XORRECORD 1 "Version 1.4.3, Mar 18, 2016"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -527,6 +527,25 @@ Afterwards end emulation without performing any drive operation.
|
||||
Only if used as first command line argument this option
|
||||
prevents reading and interpretation of startup files. See section FILES below.
|
||||
.TP
|
||||
\fBdrive_scsi_dev_family=sr|sdc|sg|default\fR
|
||||
GNU/Linux specific:
|
||||
.br
|
||||
By default, cdrskin 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.
|
||||
.br
|
||||
The global lock is not applied to device files /dev/sg* and also not with
|
||||
the system calls read(2), write(2). But ioctl(SG_IO) is affected, which is
|
||||
needed to perform the SCSI commands for optical burning.
|
||||
.br
|
||||
So for simultaneous burn runs on modern GNU/Linux it is advisable to use
|
||||
drive_scsi_dev_family="sg". The drive addresses may then well be given as
|
||||
/dev/sr* but will nevertheless get used as /dev/sg*.
|
||||
.TP
|
||||
\fB--grow_overwriteable_iso\fR
|
||||
Enable emulation of multi\-session writing on overwriteable media which
|
||||
contain an ISO 9660 filesystem. This emulation is learned from growisofs \-M
|
||||
@ -589,7 +608,8 @@ reaches a given low percentage value.
|
||||
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
|
||||
different burners with Linux kernels like 3.16, if one has reason not to fix
|
||||
the problem by drive_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
|
||||
|
Reference in New Issue
Block a user