linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Afzal Mohammed <afzal.mohd.ma@gmail.com>
To: yalin wang <yalin.wang2010@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 13:53:48 +0000	[thread overview]
Message-ID: <20150824134148.GA3394@afzalpc> (raw)
In-Reply-To: <F9B74F97-EF3F-4051-B54B-B6CDD2946374@gmail.com>

Hi,

On Mon, Aug 24, 2015 at 04:31:13PM +0800, yalin wang wrote:
> 
> i only submit the bit reverse patch for arm / arm64 arch,

yes, saw later git blaming it on you :)

> > 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.

The above measurement was done not in Linux, rather on a baremetal
code, but seeing the efficient Kernel C implementation, realized that
the gain would not be that much, it would be good to know if there are
measurements for Kernel bitreversal in C & asm (on supported arch)

Regards
afzal

      reply	other threads:[~2015-08-24 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 10:12 [RFC] fbdev/riva:change to use generice function to implement reverse_order() 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
2015-08-24 13:53               ` Afzal Mohammed [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=20150824134148.GA3394@afzalpc \
    --to=afzal.mohd.ma@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=yalin.wang2010@gmail.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;
as well as URLs for NNTP newsgroup(s).