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>
Subject: Re: [PATCH v3 0/2] clocksource/drivers/dw_apb_timer: improve performance a bit
Date: Wed, 25 Nov 2015 23:50:49 +0800 [thread overview]
Message-ID: <20151125235049.1d742846@xhacker> (raw)
In-Reply-To: <1448466514-5298-1-git-send-email-jszhang@marvell.com>
On Wed, 25 Nov 2015 23:48:32 +0800
Jisheng Zhang wrote:
> These two patches try to improve the dw_apb_timer clocksource/clockevent
> performance.
These patches depends on the apbt_readl return value fix patch:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/388250.html
thanks,
Jisheng
>
> 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(-)
>
prev parent reply other threads:[~2015-11-25 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:48 [PATCH v3 0/2] clocksource/drivers/dw_apb_timer: improve performance a bit Jisheng Zhang
2015-11-25 15:48 ` [PATCH v3 1/2] clocksource/drivers/dw_apb_timer: Inline apbt_readl and apbt_writel Jisheng Zhang
2015-11-25 15:48 ` [PATCH v3 2/2] clocksource/drivers/dw_apb_timer: Use {readl|writel}_relaxed in critical path Jisheng Zhang
2015-11-25 15:50 ` Jisheng Zhang [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=20151125235049.1d742846@xhacker \
--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