From: Lee Revell <rlrevell@joe-job.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: old radeon latency problem still unfixed?
Date: Sun, 26 Feb 2006 19:32:50 -0500 [thread overview]
Message-ID: <1141000370.24141.237.camel@mindpipe> (raw)
In-Reply-To: <1140999499.3982.17.camel@localhost.localdomain>
On Mon, 2006-02-27 at 11:18 +1100, Benjamin Herrenschmidt wrote:
> On Sun, 2006-02-26 at 18:02 -0500, Lee Revell wrote:
> > On Mon, 2006-02-27 at 09:53 +1100, Benjamin Herrenschmidt wrote:
> > > Well... as soon as a 3d window appears, the server starts switching
> > > all the time. there might be some spin loop in there remaining...
> >
> > But if the only lock taken in the radeon driver is the BKL, the
> > SCHED_NORMAL X server should not be able to delay a SCHED_FIFO process
> > right?
>
> If you have preempt enabled, I suppose .... can we preempt with the BKL
> nowadays ?
Yes.
This seems to have been user error - old kernel and/or broken config.
Until I get more feedback from the user, this can probably be
disregarded.
Lee
next prev parent reply other threads:[~2006-02-27 0:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 1:36 old radeon latency problem still unfixed? Lee Revell
2006-02-26 2:33 ` Fernando Lopez-Lezcano
2006-02-26 2:36 ` Lee Revell
2006-02-26 9:13 ` Arjan van de Ven
2006-02-26 19:35 ` Lee Revell
2006-02-26 21:11 ` Benjamin Herrenschmidt
2006-02-26 21:31 ` Lee Revell
2006-02-26 22:53 ` Benjamin Herrenschmidt
2006-02-26 23:02 ` Lee Revell
2006-02-27 0:18 ` Benjamin Herrenschmidt
2006-02-27 0:32 ` Lee Revell [this message]
2006-02-26 9:44 ` Andrew Morton
2006-02-26 9:57 ` Arjan van de Ven
2006-02-26 19:39 ` Lee Revell
2006-02-26 21:31 ` Dave Airlie
2006-02-26 21:35 ` Lee Revell
2006-02-26 22:09 ` Dave Airlie
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=1141000370.24141.237.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=arjan@infradead.org \
--cc=benh@kernel.crashing.org \
--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