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: Tue, 1 Apr 2014 17:46:54 -0500 [thread overview]
Message-ID: <20140401224654.GA23786@saruman.home> (raw)
In-Reply-To: <1396392259-27437-1-git-send-email-balbi@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2068 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 ;-)
>
> drivers/irqchip/irq-crossbar.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/irqchip/irq-crossbar.c b/drivers/irqchip/irq-crossbar.c
> index fc817d2..1c4da5a 100644
> --- a/drivers/irqchip/irq-crossbar.c
> +++ b/drivers/irqchip/irq-crossbar.c
> @@ -31,6 +31,7 @@ struct crossbar_device {
> void __iomem *crossbar_base;
> int *register_offsets;
> void (*write) (int, int);
> + unsigned int current_irq;
> };
>
> static struct crossbar_device *cb;
> @@ -52,16 +53,15 @@ static inline void crossbar_writeb(int irq_no, int cb_no)
>
> static inline int allocate_free_irq(int cb_no)
> {
> - int i;
> + int current_irq;
>
> - for (i = 0; i < cb->int_max; i++) {
> - if (cb->irq_map[i] == IRQ_FREE) {
> - cb->irq_map[i] = cb_no;
> - return i;
> - }
> - }
> + if (cb->current_irq == cb->int_max)
> + return -ENODEV;
> +
> + current_irq = cb->current_irq++;
> + cb->irq_map[current_irq++] = cb_no;
this increment is bogus, thought I had committed already, please ignore.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-01 22:49 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 [this message]
2014-04-10 21:55 ` Felipe Balbi
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=20140401224654.GA23786@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