All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <daenzer@debian.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>
Subject: Re: PREEMPT on PPC
Date: Mon, 29 Mar 2004 11:55:45 +1000	[thread overview]
Message-ID: <1080525344.1209.53.camel@gaston> (raw)
In-Reply-To: <1080524303.2441.108.camel@thor.asgaard.local>


> Note that I'm not sure how tightly the problems are tied to swap; after
> they start, they seem to persist even when swap is no longer used. It's
> just the best criterion I've been able to identify so far.

Weird. I just can't reproduce any of your problems, neither on the
tipb with highmem & lots of RAM, or on the wallstreet with no highmem
and little RAM (thus swap)...

I've been running with preempt for a few days now without trouble.

What else are you using ? I suspect something like MOL may have troubles
with preempt for example...

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-03-29  1:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25  6:47 PREEMPT on PPC Benjamin Herrenschmidt
2004-03-25  8:01 ` Benjamin Herrenschmidt
2004-03-25 16:09   ` Colin Leroy
2004-03-25 22:42     ` Benjamin Herrenschmidt
2004-03-26 17:48   ` Michael Schmitz
2004-03-26 19:27     ` Michel Dänzer
2004-03-27  9:14       ` Mathieu Segaud
2004-03-27 15:05   ` Michel Dänzer
2004-03-29  1:26     ` Benjamin Herrenschmidt
2004-03-29  1:38       ` Michel Dänzer
2004-03-29  1:55         ` Benjamin Herrenschmidt [this message]
2004-03-29  9:31           ` Michael Schmitz
2004-03-29 10:43           ` Michel Dänzer
2004-03-29 11:29             ` Michael Schmitz
2004-03-29 12:01               ` Benjamin Herrenschmidt
2004-03-29 12:00             ` Benjamin Herrenschmidt

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=1080525344.1209.53.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=daenzer@debian.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.