From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: <linux-fbdev-devel@sourceforge.net>,
Cort Dougan <cort@fsmlabs.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [prepatches] removal of console_lock
Date: Mon, 5 Mar 2001 15:36:54 +0100 [thread overview]
Message-ID: <19350128080838.10672@mailhost.mipsys.com> (raw)
In-Reply-To: <3AA38E05.549BCF95@uow.edu.au>
In-Reply-To: <3AA38E05.549BCF95@uow.edu.au>
>Cort Dougan wrote:
>>
>> I still get huge over-runs with fbdev (much improved, though).
>
>If you're referring to scheduling overruns then yes, you will
>still see monstrous ones. We're still spending great lengths of
>time in the kernel, only now we're doing it with interrupts
>enabled. We can still block all tasks for half a second at a time.
Well, at least having interrupts enabled is really nice for us on PPC
since we have this nasty chip (the PMU) that don't like at all beeing
interrupted for a long time in the middle of a message exchange.
It has caused endless trouble in the past and still, occasionally, when
you set your powerbook display bit depth to 32 and don't enable HW
acceleration in the fbdev driver.
I hope your patch will be merged in as soon as possible :) I'll do some
tests here.
Ben.
next prev parent reply other threads:[~2001-03-05 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 7:31 [prepatches] removal of console_lock Andrew Morton
2001-03-04 10:26 ` Pierre Rousselet
2001-03-04 10:42 ` Andrew Morton
2001-03-05 6:15 ` Cort Dougan
2001-03-05 13:00 ` Andrew Morton
2001-03-05 14:36 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-04 10:57 Manfred Spraul
2001-03-04 11:19 ` Andrew Morton
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=19350128080838.10672@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=andrewm@uow.edu.au \
--cc=cort@fsmlabs.com \
--cc=linux-fbdev-devel@sourceforge.net \
--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