From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Floating point in the kernel
Date: Fri, 11 Dec 2009 07:56:48 +1100 [thread overview]
Message-ID: <1260478608.16132.263.camel@pasglop> (raw)
In-Reply-To: <20091210153359.3a480488@lappy.seanm.ca>
On Thu, 2009-12-10 at 15:33 -0500, Sean MacLennan wrote:
> To be honest, I can't find *why* we are scheduling :( They only way we
> give up the CPU is with locking... and none of the locks where hit
> during the problem. We also never get near our timeslice... the
> longest
> run I saw when the problem happened was 670us.
>
> Is there a way to disable scheduling? We currently do not have preempt
> enabled... but may in the future.
Well, that would be interesting to see where you schedule indeed.
Outside of preempt and an explicit lock or memory allocation I don't
see ... Or get/put_user ?
Cheers,
Ben.
next prev parent reply other threads:[~2009-12-10 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 18:13 Floating point in the kernel Sean MacLennan
2009-12-10 20:19 ` Benjamin Herrenschmidt
2009-12-10 20:33 ` Sean MacLennan
2009-12-10 20:56 ` Benjamin Herrenschmidt [this message]
2009-12-10 21:35 ` Arnd Bergmann
2009-12-11 0:17 ` Sean MacLennan
2009-12-11 11:28 ` Arnd Bergmann
2009-12-10 20:32 ` arnd
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=1260478608.16132.263.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
/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.