From: Clemens Ladisch <clemens@ladisch.de>
To: Keith Chew <keith.chew@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: PCM multi A/V Sync bug on SMP system
Date: Fri, 30 Apr 2010 13:09:12 +0200 [thread overview]
Message-ID: <4BDABA58.3090200@ladisch.de> (raw)
In-Reply-To: <y2l20f65d531004281312ja49b333eha47fd0cb9c5b0e01@mail.gmail.com>
Keith Chew wrote:
> In pcm_dmix_i386.c, we have:
>
> if (!strncmp(line, "processor", 9))
> smp++;
>
> I have commented out the smp++, so that it thinks that I am on a uni
> processor. Voila, so AV sync issues!
>
> My question now is what are the implications of this change? Looking
> at pcm_dmix_i386.h, it uses locks on an SMP system, but exclude them
> if not SMP. Do we still need this lock, even if I am on a dual core,
> ie 1 processor 2 cores?
Dual-core processors behave like two separate processors, i.e., they
still have separate caches, so we still need to synchronize memory
accesses to ensure that they happen in the correct order.
I'd guess that the memory bus synchronization of the three dmix devices
makes the memory accesses too slow. What is the CPU utilization of
mplayer with and without SMP?
Regards,
Clemens
prev parent reply other threads:[~2010-04-30 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 5:07 PCM multi A/V Sync bug on SMP system Keith Chew
2010-04-27 19:28 ` Keith Chew
2010-04-28 20:12 ` Keith Chew
2010-04-30 11:09 ` Clemens Ladisch [this message]
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=4BDABA58.3090200@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=keith.chew@gmail.com \
/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).