From: joerg.krause@embedded.rocks (Jörg Krause)
To: linux-arm-kernel@lists.infradead.org
Subject: mmc: core: complete/wait_for_completion performance
Date: Thu, 15 Dec 2016 14:50:14 +0100 [thread overview]
Message-ID: <1481809814.29241.2.camel@embedded.rocks> (raw)
In-Reply-To: <962480933.163666.1481741832090@email.1und1.de>
Hi Stefan,
On Wed, 2016-12-14 at 19:57 +0100, Stefan Wahren wrote:
> Hi J?rg,
>
[snip]
> > >
> > > did you try cyclictest [1]?
> >
> > Not yet. Not sure what to measure and which values to compare here.
>
> i tought you have the vendor kernel and the mainline kernel available
> for your platform.
>
> So you could compare the both kernels.
Yes, that's right. I will have a look at this tool.
> >
> > >
> > > Beside the time for a request the amount of requests for the
> > > complete
> > > iperf test
> > > would we interesting. Maybe there are retries.
> > >
> > > I'm still interested in your PIO mode patches for mxs-mmc even
> > > without clean up.
> >
> > Actually, the patch does not implement a PIO mode, but drops DMA
> > and
> > uses polling instead. I've attached the patch.
>
> Thanks. I applied it, but unfortunately this breaks SD card support
> for my Duckbill and the kernel isn't able to mount the rootfs:
>
> [????2.267073] mxs-mmc 80010000.ssp: initialized
> [????2.272624] mxs-mmc 80010000.ssp: AC command error 0xffffff92
Sorry, I messed up the branches. I attached the correct patch which is
working for me on Linux v4.9.
J?rg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0200-mmc-mxs-mmc-use-PIO-mode.patch
Type: text/x-patch
Size: 15450 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161215/b5c33807/attachment-0001.bin>
next prev parent reply other threads:[~2016-12-15 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 12:27 mmc: core: complete/wait_for_completion performance Jörg Krause
2016-11-20 13:28 ` Stefan Wahren
2016-11-20 14:42 ` Jörg Krause
2016-11-20 15:44 ` Stefan Wahren
2016-11-20 19:10 ` Jörg Krause
2016-11-26 19:10 ` Stefan Wahren
2016-12-07 7:29 ` Jörg Krause
2016-12-07 7:32 ` Jörg Krause
2016-12-07 19:23 ` Stefan Wahren
2016-12-14 9:03 ` Jörg Krause
2016-12-14 18:57 ` Stefan Wahren
2016-12-15 13:50 ` Jörg Krause [this message]
2016-12-15 18:51 ` Stefan Wahren
2016-12-16 10:06 ` Jörg Krause
2016-12-26 23:03 ` Stefan Wahren
[not found] ` <1484512950.2026.4.camel@embedded.rocks>
2017-01-15 21:08 ` Stefan Wahren
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=1481809814.29241.2.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.