qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] alsaaudio: increase default buffer sizes
Date: Tue, 6 May 2008 21:37:13 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805062130540.2419@linmac.oyster.ru> (raw)
In-Reply-To: <481F554B.1020100@web.de>

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 need
>>> more under certain guest load, but now I'm already fine with
>>> DEFAULT_BUFFER_SIZE=4096. Or all in one:
>>
>> I wonder if everyone will be happy with quadrupled latency, apart from
>
> Hmm, I wonder about the scenario where this latency may actually hurt.
> QEMU is not /that/ fast anyway. ;)

You would be surprised.

>
>> 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=alsa (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?

> - possibly have to fix up your configuration with FIXED_FREQ and
>   BUFFER_SIZE (as reported by >1 kvm users) until
>
> As OSS does not give us shared sound device access and, in the end, is a
> deprecated API under Linux, my goal is to overcome remaining issues of
> the ALSA support and then make /this/ the default one (under Linux).
>

Huh? Even OSS/lite that is/was shipping with default Linux gave me
"shared" sound, though i had a decent sound card with possibility to
open the same /dev/dsp 16 times (it actually had 16 sigmatel chips on
board). And the real OSS has vmix. And fwiw to have this wonderful
"shared" sound you have to configure "dmix" (or whatever its called)
too.

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2008-05-06 17:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 19:06 [Qemu-devel] [PATCH] alsaaudio: increase default buffer sizes Jan Kiszka
2008-05-02 19:48 ` [Qemu-devel] " malc
2008-05-02 21:00   ` Jan Kiszka
2008-05-03 19:43     ` malc
2008-05-04  7:34       ` Jan Kiszka
2008-05-04 17:09         ` malc
2008-05-04 17:41           ` Jan Kiszka
2008-05-04 19:35             ` Jan Kiszka
2008-05-05 18:03               ` malc
2008-05-05 18:43                 ` Jan Kiszka
2008-05-06 17:37                   ` malc [this message]
2008-05-06 17:59                     ` Jan Kiszka
2008-05-07 18:36                       ` malc
2008-05-07 22:24                         ` Jan Kiszka
2008-05-08 17:44                           ` malc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0805062130540.2419@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).