public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Felix Radensky <felix@embedded-sol•com>
Subject: Re: Preemption question (4xx related)
Date: Thu, 02 Jul 2009 11:14:29 +0200	[thread overview]
Message-ID: <1246526069.7938.1542.camel@thor> (raw)
In-Reply-To: <1246486393.14483.14.camel@pasglop>

On Thu, 2009-07-02 at 08:13 +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2009-06-30 at 05:55 -0700, Felix Radensky wrote:
> > Hi,
> >=20
> > Preemption is disabled on the vast majority of powerpc
> > targets. Are there any known problems in this area ?
> > I'd like to enable CONFIG_PREEMPT_VOLUNTARY on
> > AMCC 405EX target, to increase application responsiveness.
> > Is it a bad idea ?
>=20
> In theory it should work, but as you may have noticed, it's generally
> disabled and thus not very well tested.
>=20
> It would be a good idea for us, some of the core devs, to turn that on
> in our usual test configs in fact.

FWIW, on my PowerBook I've been running with CONFIG_PREEMPT_VOLUNTARY
enabled for a long time (more than a year). No problems so far, and it
definitely seems to help a lot for interactivity.


--=20
Earthling Michel D=C3=A4nzer           |                http://www.vmware.c=
om
Libre software enthusiast         |          Debian, X and DRI developer

      parent reply	other threads:[~2009-07-02  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 12:55 Preemption question (4xx related) Felix Radensky
2009-07-01 22:13 ` Benjamin Herrenschmidt
2009-07-02  0:14   ` Josh Boyer
2009-07-02  7:33     ` Benjamin Herrenschmidt
2009-07-02 11:12       ` Josh Boyer
2009-07-02 22:41         ` Benjamin Herrenschmidt
2009-07-03  0:34           ` Josh Boyer
2009-07-02  9:14   ` Michel Dänzer [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=1246526069.7938.1542.camel@thor \
    --to=michel@daenzer$(echo .)net \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=felix@embedded-sol$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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