oysteikt/mpd
0
0
Fork 0
Code Issues Pull Requests Releases Activity

output/alsa: remove option "use_mmap"

Browse Source 
MPD does not really take advantage of memory-mapped I/O by generating
data right into the ALSA buffer; using plain snd_pcm_mmap_writei() has
no advantage compared to snd_pcm_writei().  Let's kill this
non-feature.
This commit is contained in:
Max Kellermann
2016-02-28 09:30:59 +01:00
parent 111528e51c
commit 8ffcdb73e8
4 changed files with 9 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/mpd.conf.5
View File

@@ -238,11 +238,6 @@ probably only useful if your alsa device has more than one
identically\-named mixer control. The default is "0". Use "amixer
scontrols" to see the list of controls with their indexes.
.TP
.B use_mmap <yes or no>
Setting this allows you to use memory-mapped I/O. Certain hardware setups may
benefit from this, but most do not. Most users do not need to set this. The
default is to not use memory-mapped I/O.
.TP
.B auto_resample <yes or no>
Setting this to "no" disables ALSA's software resampling, if the
hardware does not support a specific sample rate. This lets MPD do

11
doc/user.xml
View File

@@ -2482,17 +2482,6 @@ buffer_size: 16384</programlisting>
...).
</entry>
</row>
<row>
<entry>
<varname>use_mmap</varname>
<parameter>yes|no</parameter>
</entry>
<entry>
If set to <parameter>yes</parameter>, then
<filename>libasound</filename> will try to use
memory mapped I/O.
</entry>
</row>
<row>
<entry>
<varname>buffer_time</varname>