From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marek.vasut@gmail.com>,
kernel list <linux-kernel@vger.kernel.org>,
Dinh Nguyen <dinh.linux@gmail.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Jingoo Han <jg1.han@samsung.com>, Rob Clark <robdclark@gmail.com>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
shc_work@mail.ru, linux@arm.linux.org.uk,
hsweeten@visionengravers.com,
Archit Taneja <architt@codeaurora.org>
Subject: Re: simple framebuffer slower by factor of 20, on socfpga (arm) platform
Date: Thu, 09 Apr 2015 11:21:43 +0000 [thread overview]
Message-ID: <552660C7.4020805@ti.com> (raw)
In-Reply-To: <20150409110634.GA27407@amd>
[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]
On 09/04/15 14:06, Pavel Machek wrote:
> On Tue 2015-04-07 14:19:33, Geert Uytterhoeven wrote:
>> Hi Pavel,
>>
>> On Tue, Apr 7, 2015 at 2:12 PM, Pavel Machek <pavel@ucw.cz> wrote:
>>> I have an socfpga board, which uses has simple framebuffer implemented
>>> in the FPGA. On 3.15, framebuffer is fast:
>>>
>>> root@wagabuibui:~# time cat /dev/fb0 > /dev/null
>>> real 0m 0.00s
>>> user 0m 0.00s
>>> sys 0m 0.00s
>>>
>>> on 3.18, this takes 220msec. Similar slowdown exists for
>>> writes. Simple framebuffer did not change at all between 3.15 and
>>> 3.18; resource flags of the framebuffer are still same (0x200).
>>>
>>> If I enable caching on 3.18, it speeds up a bit, to 70msec or
>>> so... Which means problem is not only in caching.
>>>
>>> Any ideas?
>>
>> My first guess was commit 67dc0d4758e5 ("vt_buffer: drop console buffer
>> copying optimisations"), but this was introduced only in v4.0-rc1.
>>
>> Just in case you encounter another performance regression after upgrading
>> to a more modern kernel ;-)
>
> :-). I did a git bisect, and it pointed to this. And reverting it
> indeed fixes the problem in 3.18. Problem is still there in 4.0.
Interesting. I can reproduce this also on TI's AM437x board, on 3.14
kernel. Without the patch:
# time cat /dev/fb0 > /dev/null
real 0m 0.01s
user 0m 0.00s
sys 0m 0.01s
With the patch:
# time cat /dev/fb0 > /dev/null
real 0m 0.19s
user 0m 0.01s
sys 0m 0.17s
> Archit do you know what is going on there? Should the revert be filled
> for 4.0?
(Cc'ing Archit's new email)
>
> Pavel
>
> commit 981409b25e2a99409b26daa67293ca1cfd5ea0a0
> Author: Archit Taneja <archit@ti.com>
> Date: Fri Nov 16 14:46:04 2012 +0530
>
> fbdev: arm has __raw I/O accessors, use them in fb.h
>
> This removes the sparse warnings on arm platforms:
>
> warning: cast removes address space of expression
>
> Signed-off-by: Archit Taneja <archit@ti.com>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Cc: H Hartley Sweeten <hsweeten at visionengravers.com>
> Cc: Alexander Shiyan <shc_work@mail.ru>
> Cc: Russell King <linux@arm.linux.org.uk>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-04-09 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:12 simple framebuffer slower by factor of 20, on socfpga (arm) platform Pavel Machek
2015-04-07 12:19 ` Geert Uytterhoeven
2015-04-07 14:24 ` Marek Vasut
2015-04-09 11:06 ` Pavel Machek
2015-04-09 11:21 ` Tomi Valkeinen [this message]
2015-04-09 11:34 ` Tomi Valkeinen
[not found] ` <552663C2.70308-l0cyMroinI0@public.gmane.org>
2015-04-09 19:51 ` Arnd Bergmann
2015-04-24 13:31 ` Pavel Machek
2015-04-10 7:17 ` Archit Taneja
2015-04-24 13:29 ` Pavel Machek
2015-04-24 13:40 ` Tomi Valkeinen
2015-04-24 13:46 ` Geert Uytterhoeven
2015-04-26 19:31 ` Pavel Machek
2015-04-28 13:48 ` Russell King - ARM Linux
[not found] ` <20150428134848.GC12732-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-04-28 15:28 ` Nicolas Pitre
2015-05-06 10:45 ` Russell King - ARM Linux
2015-05-06 20:32 ` Nicolas Pitre
2015-05-12 8:52 ` Pavel Machek
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=552660C7.4020805@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=architt@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=hsweeten@visionengravers.com \
--cc=jg1.han@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
--cc=plagnioj@jcrosoft.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shc_work@mail.ru \
/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).