From: yalin wang <yalin.wang2010@gmail.com>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
adaplas@gmail.com, plagnioj@jcrosoft.com,
linux-fbdev@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] fbdev/riva:change to use generice function to implement reverse_order()
Date: Mon, 24 Aug 2015 16:31:13 +0800 [thread overview]
Message-ID: <F9B74F97-EF3F-4051-B54B-B6CDD2946374@gmail.com> (raw)
In-Reply-To: <20150822075310.GA2337@afzalpc>
> On Aug 22, 2015, at 15:53, Afzal Mohammed <afzal.mohd.ma@gmail.com> wrote:
>
> Hi,
>
> On Fri, Aug 21, 2015 at 11:01:41AM +0300, Tomi Valkeinen wrote:
>
>>>> Possibly the patches are still good for x86 also, but that needs to be
>>>> proven.
>>>>
>>> not exactly, because x86_64 don’t have hardware instruction to do rbit OP,
>>> i compile by test :
>>
>> For old drivers i386 may be more relevant than x86_64.
>
> It seems asm bit reversal is supported in Kernel on arm & arm64 only,
> not sure whether any other arch even provide asm bit reversal
> instruction.
i only submit the bit reverse patch for arm / arm64 arch,
i am not sure if there are some other arch also have hard ware bit reverse
instructions, need arch maintainers to submit if their arch also have these hard
ware instructions . :)
>
>> These kind of optimizations should have some real world measurements,
>
> Not for this case, but once measured on ARM, iirc, a 32-bit asm bit
> reversal as compared to doing it in C was taking 1 cycle as opposed to
> ~225 cycles!, of course writing optimized C could have made it fare
> better, but still would reach no-way near asm bit reversal.
>
next prev parent reply other threads:[~2015-08-24 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 10:12 yalin wang
2015-08-20 11:02 ` Tomi Valkeinen
2015-08-20 11:30 ` yalin wang
2015-08-21 6:41 ` Tomi Valkeinen
2015-08-21 7:46 ` yalin wang
2015-08-21 8:01 ` Tomi Valkeinen
2015-08-22 7:53 ` Afzal Mohammed
2015-08-24 8:31 ` yalin wang [this message]
2015-08-24 13:41 ` Afzal Mohammed
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=F9B74F97-EF3F-4051-B54B-B6CDD2946374@gmail.com \
--to=yalin.wang2010@gmail.com \
--cc=adaplas@gmail.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
/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®