From: Fortini Matteo <matteo.fortini@mta.it>
To: Kenneth Johansson <kenneth@southpole.se>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: Acceleration for map_copy_from on powerpc 512x
Date: Tue, 27 Oct 2009 11:02:07 +0100 [thread overview]
Message-ID: <4AE6C51F.9050203@mta.it> (raw)
In-Reply-To: <1256135453.22238.27.camel@kenjo-laptop>
The simple_map_init() works at a higher level, what I'm redefining is a
function called by mtd->read()
The block size for e.g. a dd if=/dev/mtd0 of=/dev/null
with the default block size (I believe it's 512Bytes), fetches from
/dev/mtd0 4096 Bytes at a time.
I'd prefer the kernel to be scheduling other tasks meanwhile, instead of
busy-waiting on completion.
Regards
Kenneth Johansson ha scritto:
> On Mon, 2009-10-19 at 09:52 +0200, Fortini Matteo wrote:
>
>
>> I didn't find a cleaner way than just #ifdef'ing the map_copy_from call
>> and substitute with my call on relevant cases. I wonder if there is a
>> cleaner way.
>>
>
> Remove the call to simple_map_init() and do it manually in your driver
> with your own functions.
>
>
>> And yes, as soon as I've cleaned up the code a little bit, I will
>> definitely post a patch about it.
>>
>> Moreover: a huge benefit would come from exploiting DMA on these
>> transfers,
>>
>
> probably depends on the block size if it's a gain or not. What is the
> size you normally see.
>
>
>
next prev parent reply other threads:[~2009-10-27 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 7:52 Acceleration for map_copy_from on powerpc 512x Fortini Matteo
2009-10-21 14:30 ` Kenneth Johansson
2009-10-27 10:02 ` Fortini Matteo [this message]
2009-10-27 11:41 ` Kenneth Johansson
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=4AE6C51F.9050203@mta.it \
--to=matteo.fortini@mta.it \
--cc=kenneth@southpole.se \
--cc=linuxppc-dev@ozlabs.org \
/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).