Embedded Linux development
 help / color / mirror / Atom feed
From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
	linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Project Proposal: add sleeping spinlocks to mainline kernel
Date: Thu, 17 Dec 2009 10:54:23 +0100	[thread overview]
Message-ID: <63386a3d0912170154k6521433fl90b2ae96efb70a34@mail.gmail.com> (raw)
In-Reply-To: <4B296390.3090004@am.sony.com>

2009/12/16 Tim Bird <tim.bird@am.sony.com>:

> Summary: add sleeping spinlocks to the mainline kernel

If realtime performance overall is a big deal for CELF I would suggest
adding "Kill-the-BKL" to the suggested projects. There are still some
RTOS people using the BKL as an argument to flak the Linux kernel,
c.f.
http://www.freescale.com/files/32bit/doc/ref_manual/EMBMCRM.pdf
(section 5.2)

Another item could be to go through some common embedded
arch drivers and switch them from request_irq() to request_threaded_irq()
just based on the observation that almost nobody actually use that
in the mainline kernel, though I'm sure they should,
if realtime is a desired feature.
(The wm8350-core driver is an excellent example of a situation where
it is used properly.)

NB: I'm not a member of the CE Linux Forum and nor is my company
so I'm just talking freely here. (linux-embedded is public, hehe.)

Yours,
Linus Walleij

  reply	other threads:[~2009-12-17  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 22:47 Project Proposal: add sleeping spinlocks to mainline kernel Tim Bird
2009-12-17  9:54 ` Linus Walleij [this message]
2009-12-17 18:45   ` Tim Bird

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=63386a3d0912170154k6521433fl90b2ae96efb70a34@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=celinux-dev@tree.celinuxforum.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox