From: Jisheng Zhang <jszhang@marvell.com>
To: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>, <arnd@arndb.de>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH v4 0/2] clocksource/drivers/dw_apb_timer: improve performance a bit
Date: Thu, 26 Nov 2015 00:01:51 +0800 [thread overview]
Message-ID: <1448467313-5626-1-git-send-email-jszhang@marvell.com> (raw)
These two patches try to improve the dw_apb_timer clocksource/clockevent
performance.
These patches depend on the apbt_readl return value fix patch:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/388250.html
since v3:
- fix commit msg: we measured 4096 rounds of function call. So add this
information into commit msg to avoid confusion.
since v2:
- only use relaxed version in critical path
- inline apbt_readl/apbt_writel
- add some performance numbers
since v1:
- correct the wrong sentence in commit msg about writel performance on
CA9 with outer L2 cache. Thank Arnd for pointing out this in another
thread.
Jisheng Zhang (2):
clocksource/drivers/dw_apb_timer: Inline apbt_readl and apbt_writel
clocksource/drivers/dw_apb_timer: Use {readl|writel}_relaxed in
critical path
drivers/clocksource/dw_apb_timer.c | 30 +++++++++++++++++++++---------
1 file changed, 21 insertions(+), 9 deletions(-)
--
2.6.2
next reply other threads:[~2015-11-25 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 16:01 Jisheng Zhang [this message]
2015-11-25 16:01 ` [PATCH v4 1/2] clocksource/drivers/dw_apb_timer: Inline apbt_readl and apbt_writel Jisheng Zhang
2015-11-25 16:01 ` [PATCH v4 2/2] clocksource/drivers/dw_apb_timer: Use {readl|writel}_relaxed in critical path Jisheng Zhang
2015-12-15 20:42 ` [PATCH v4 0/2] clocksource/drivers/dw_apb_timer: improve performance a bit Daniel Lezcano
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=1448467313-5626-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).