From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Marc Zyngier <marc.zyngier@arm.com>, linux-kernel@vger.kernel.org
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>, stable@vger.kernel.org
Subject: [PATCH 0/4] irqchip/gic-v3-its: free_lpi_range tweaks
Date: Tue, 12 Mar 2019 18:33:45 +0100 [thread overview]
Message-ID: <20190312173350.4025-1-linux@rasmusvillemoes.dk> (raw)
I noticed that the O(n log n) behaviour of free_lpi_range could easily
be made O(n) (patch 4), though I don't suppose n is ever large enough
to actually matter. While there, I also stumbled on two other
micro-optimizations (2 and 3).
Then while writing the commit log for the last patch, I noticed that
the cmp callback I was removing was actually buggy, so I went back and
added a patch in front suitable for -stable. I'll leave it to others
to decide if it's important enough for that.
Please note that this is only compile-tested.
Rasmus Villemoes (4):
irqchip/gic-v3-its: fix comparison logic in lpi_range_cmp
irqchip/gic-v3-its: move allocation outside mutex
irqchip/gic-v3-its: drop redundant initialization in mk_lpi_range
irqchip/gic-v3-its: make free_lpi_range a little cheaper
drivers/irqchip/irq-gic-v3-its.c | 75 +++++++++++++++-----------------
1 file changed, 36 insertions(+), 39 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-12 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:33 Rasmus Villemoes [this message]
2019-03-12 17:33 ` [PATCH 1/4] irqchip/gic-v3-its: fix comparison logic in lpi_range_cmp Rasmus Villemoes
2019-03-12 17:33 ` [PATCH 2/4] irqchip/gic-v3-its: move allocation outside mutex Rasmus Villemoes
2019-03-12 17:33 ` [PATCH 3/4] irqchip/gic-v3-its: drop redundant initialization in mk_lpi_range Rasmus Villemoes
2019-03-12 17:33 ` [PATCH 4/4] irqchip/gic-v3-its: make free_lpi_range a little cheaper Rasmus Villemoes
2019-03-12 18:03 ` [PATCH 0/4] irqchip/gic-v3-its: free_lpi_range tweaks Marc Zyngier
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=20190312173350.4025-1-linux@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®