From: Stan Bubrouski <stan@ccs.neu.edu>
To: Andi Kleen <ak@muc.de>
Cc: Malte Schr?der <MalteSch@gmx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bad X-performance on 2.6.6 & 2.6.7-rc1 on x86-64
Date: Tue, 25 May 2004 17:20:22 -0400 [thread overview]
Message-ID: <1085520021.1393.4168.camel@duergar> (raw)
In-Reply-To: <20040525123636.GA13817@colin2.muc.de>
On Tue, 2004-05-25 at 08:36, Andi Kleen wrote:
> On Tue, May 25, 2004 at 12:26:59PM +0200, Malte Schr?der wrote:
> > New information :)
> > I didn't profile it yet but I think I found what caused the problem.
> > It turned out that I have to disable alsa mmap-support in xine (mplayer worked w/o problems, it does not offer alsa mmap), so X is not involved at all. Do you still need a profile or is this a known thing?
>
> Ask the xine guys if it's known, I don't know much about xine.
> If a user space change fixes it then I don't need any profiles.
>
I can confirm that xine with alsa-mmap option set does cuase strange
behaviour, though I notice it mostly as audio and video getting out of
sync when playing videos. I've noticed this behaviour since I started
doing weekly xine CVS builds. I've never bothered reporting it however,
I just turned off the option... which leads me to my question, what is
the advantage of using alsa-mmap in an app if it is used correctly?
And Malte, are you using emu10k1 driver per chance?
-sb
> -Andi
next prev parent reply other threads:[~2004-05-25 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ZqbC-5Gl-13@gated-at.bofh.it>
2004-05-24 19:31 ` Andi Kleen
2004-05-25 10:26 ` Malte Schröder
2004-05-25 12:36 ` Andi Kleen
2004-05-25 21:20 ` Stan Bubrouski [this message]
2004-05-25 21:32 ` Tomasz Torcz
2004-05-26 10:28 ` Malte Schröder
2004-05-26 10:26 ` Malte Schröder
2004-05-26 23:51 ` Stan Bubrouski
2004-05-27 8:57 ` Malte Schröder
2004-05-24 16:00 Malte Schröder
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=1085520021.1393.4168.camel@duergar \
--to=stan@ccs.neu.edu \
--cc=MalteSch@gmx.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®