From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jts4X-0002ac-Gw for qemu-devel@nongnu.org; Wed, 07 May 2008 18:25:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jts4V-0002aK-IJ for qemu-devel@nongnu.org; Wed, 07 May 2008 18:25:12 -0400 Received: from [199.232.76.173] (port=51553 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jts4V-0002aH-AL for qemu-devel@nongnu.org; Wed, 07 May 2008 18:25:11 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:38251) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jts4U-00078l-Oc for qemu-devel@nongnu.org; Wed, 07 May 2008 18:25:11 -0400 Message-ID: <48222C3A.1050607@web.de> Date: Thu, 08 May 2008 00:24:58 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <481B6626.7010603@web.de> <481B80F0.8050705@web.de> <481D670D.6070602@web.de> <481DF561.4050709@web.de> <481E1001.3010703@web.de> <481F554B.1020100@web.de> <48209C67.9010801@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0CEAA22EEEE2A67CD0D3B488" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [PATCH] alsaaudio: increase default buffer sizes Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: malc Cc: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0CEAA22EEEE2A67CD0D3B488 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable malc wrote: > On Tue, 6 May 2008, Jan Kiszka wrote: >=20 >> malc wrote: >>> On Mon, 5 May 2008, Jan Kiszka wrote: >>> >>>> malc wrote: >>>>> On Sun, 4 May 2008, Jan Kiszka wrote: >>>>> >>>>>> Jan Kiszka wrote: >>>>>>> malc wrote: >>>>>>>> On Sun, 4 May 2008, Jan Kiszka wrote: >>>>>>>> >>>>> >>>>> [..snip..] >>>>> >>>>>>> >>>>>>> Yeah, great, that was the key! Find below the version that works >>>>>>> for me >>>>>>> (on 64 bit 8) ). It even obsoletes my buffer size patch. Please >>>>>>> merge! >>>>>> >>>>>> Declaring the buffer size tweak obsolete was too quick. I still ne= ed >>>>>> more under certain guest load, but now I'm already fine with >>>>>> DEFAULT_BUFFER_SIZE=3D4096. Or all in one: >>>>> >>>>> I wonder if everyone will be happy with quadrupled latency, apart f= rom >>>> >>>> Hmm, I wonder about the scenario where this latency may actually hur= t. >>>> QEMU is not /that/ fast anyway. ;) >>> >>> You would be surprised. >> >> Tell me more! :-> >=20 > The only thing that i care about: DOS demos and to lesser extent old DO= S > games. And those suffer audibly if you increase QEMU_ALSA_DAC_BUFFER_SIZE? >=20 >>> >>>> >>>>> you and this other user on some (kvm was it) mailing list there are= no >>>>> huge outcries of dissatisfaction, then again i'm not sure how many >>>>> people >>>>> use ALSA+QEMU or QEMUs+AUDIO in general. >>>> >>>> I don't think many users are actually running QEMU (or KVM) against >>>> ALSA. You have to >>>> - manually enable it during configure >>>> - pass QEMU_AUDIO_DRV=3Dalsa (OSS remains default even if ALSA is on= - I >>>> ran into this trap first.) >>> >>> I don't see how it's a trap. You can also enable esd or fmod drivers >>> in configure along with alsa, which one should be the default? >> >> For sure, you need this mechanism with >1 audio backends being enabled= >> in parallel. It's just the question how one is supposed to find out >> about this additional requirement: >=20 > Being enabled? Did you mean being built in? And what do you mean by > mechanism, mechanism to do what exactly? Yes, I meant built-in. >=20 >> $ grep -r QEMU_AUDIO_DRV qemu >> qemu/audio/audio.c: " set QEMU_AUDIO_DRV=3Dwav\n" >> qemu/audio/audio.c: " export QEMU_AUDIO_DRV=3Dwav\n" >> qemu/audio/audio.c: drvname =3D audio_get_conf_str >> ("QEMU_AUDIO_DRV", NULL, &def); >> >> Am I missing some reference? Then sorry in advance. >=20 > What is the question? Such kind of documentation is not for wimps. You know where to find and why to use it, but does the average user do? > [..snip..] >=20 >> >> Well, probably configurable as well with compat-OSS (real OSS is dead = on >> Linux). The fact is that - not only for me - this sharing does not wor= k >> out-of-the-box with OSS, while it does with ALSA. Don't ask me why, I'= m >> not an expert on this, I'm rather looking at it from a "normal" user >> perspective. >=20 > It doesn't with ALSA on this machine, and on the machine next to this > one, and on machine that lies on the floor. It boils down to how ALSA > was configured by distribution maintainers. Chances are generally higher that broken ALSA setups are reported and fixed than broken OSS emulations. Jan --------------enig0CEAA22EEEE2A67CD0D3B488 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIIiw/niDOoMHTA+kRApayAJ0QPwsfnoDXp9fSjSTU/5rXos81fQCcCBAC pJSpt9icfE5mj50J12jlHlo= =UThn -----END PGP SIGNATURE----- --------------enig0CEAA22EEEE2A67CD0D3B488--