From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: r.sricharan@ti.com, tglx@linutronix.de, galak@codeaurora.org,
santosh.shilimkar@ti.com, Darren Etheridge <detheridge@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irq: crossbar: improve allocate_free_irq() complexity
Date: Thu, 10 Apr 2014 16:55:27 -0500 [thread overview]
Message-ID: <20140410215527.GF27668@saruman.home> (raw)
In-Reply-To: <1396392259-27437-1-git-send-email-balbi@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Tue, Apr 01, 2014 at 05:44:19PM -0500, Felipe Balbi wrote:
> current algorithm in allocate_free_irq() is O(n),
> by just keeping track of last allocated IRQ with a
> simple unsigned integer, we can find a free IRQ
> in O(1).
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> ---
>
> compile-tested only as J6 DTS is currently missing crossbar
> altogether :-(
>
> There's a drawback with this patch which I'm not sure if we
> should care a lot because I couldn't entirely grasp when is
> domain->xlate() called and if we will map/unmap IRQs in runtime
> or will this *always* be done only during boot.
>
> If we're talking about runtime IRQ remapping, then this, clearly,
> won't work. But if this will be done only during boot up, then we
> avoid iterating over the irq_map array each time we try to translate
> a new IRQ prior to mapping it.
>
> Comments are highly welcome as I'll probably learn something new
> about the IRQ subsystem ;-)
do not apply this one!!! It won't work in all cases.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-04-10 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:44 [PATCH] irq: crossbar: improve allocate_free_irq() complexity Felipe Balbi
2014-04-01 22:46 ` Felipe Balbi
2014-04-10 21:55 ` Felipe Balbi [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=20140410215527.GF27668@saruman.home \
--to=balbi@ti.com \
--cc=detheridge@ti.com \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=r.sricharan@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
/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