From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: [PATCH 0/2] Two improvements to Octeon irq handling.
Date: Tue, 13 Oct 2009 08:51:05 -0700 [thread overview]
Message-ID: <4AD4A1E9.1080309@caviumnetworks.com> (raw)
The first patch is a locking correctness issue, the second an optimization.
David Daney (2):
MIPS: Octeon: Use write_lock_irqsave/write_unlock_irqrestore when
setting irq affinity.
MIPS: Octeon: Use lockless interrupt controller operations when
possible.
arch/mips/cavium-octeon/octeon-irq.c | 187
++++++++++++++++++++++++++++++++--
1 files changed, 178 insertions(+), 9 deletions(-)
next reply other threads:[~2009-10-13 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 15:51 David Daney [this message]
2009-10-13 15:52 ` [PATCH 1/2] MIPS: Octeon: Use write_lock_irqsave/write_unlock_irqrestore when setting irq affinity David Daney
2009-10-13 16:17 ` Ralf Baechle
2009-10-13 15:52 ` [PATCH 2/2] MIPS: Octeon: Use lockless interrupt controller operations when possible David Daney
2009-10-13 16:20 ` Ralf Baechle
2009-10-13 18:26 ` [PATCH] " David Daney
2009-10-13 19:41 ` Ralf Baechle
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=4AD4A1E9.1080309@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).