From: Adrian Hunter <adrian.hunter@intel.com>
To: Mason <slash.tmp@free.fr>, linux-mmc <linux-mmc@vger.kernel.org>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
Michal Simek <michal.simek@xilinx.com>,
Soren Brinkmann <soren.brinkmann@xilinx.com>,
Suman Tripathi <stripathi@apm.com>, Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
Sebastian Frias <sf84@laposte.net>
Subject: Re: mmc0: Invalid maximum block size, assuming 512 bytes
Date: Tue, 2 Feb 2016 10:58:56 +0200 [thread overview]
Message-ID: <56B06FD0.6000109@intel.com> (raw)
In-Reply-To: <56AFCEE0.1090005@free.fr>
On 01/02/16 23:32, Mason wrote:
> On 22/01/2016 08:17, Mason wrote:
>
>> On 22/01/2016 03:07, Shawn Lin wrote:
>>
>>> On 2016/1/21 23:00, Mason wrote:
>>>
>>>> So that means I have to write code in
>>>> drivers/mmc/host/sdhci-of-arasan.c correct?
>>>
>>> It depends. If you think 512 block size if okay for you, leave it alone.
>>> Otherwise, add it in drivers/mmc/host/sdhci-of-arasan.c :)
>>
>> When I measured the read/write throughput to an attached
>> SD card, I got around 16 MB/s, and I thought raising the
>> block size might help with throughput?
>>
>> I'll test and report back.
>
> Haven't had time to test yet, but I wanted to ask experienced
> folks what to expect when raising the block size from 512 to
> 2048 bytes?
mmc block driver sets block size to 512.
What you are looking at is maximum block size. SDIO uses bigger block
sizes, so it is useful for that.
next prev parent reply other threads:[~2016-02-02 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 15:33 mmc0: Invalid maximum block size, assuming 512 bytes Mason
2016-01-20 1:17 ` Shawn Lin
2016-01-21 15:00 ` Mason
2016-01-22 2:07 ` Shawn Lin
2016-01-22 7:17 ` Mason
2016-02-01 21:32 ` Mason
2016-02-02 8:58 ` Adrian Hunter [this message]
2016-02-02 10:12 ` Mason
2016-02-02 11:30 ` Adrian Hunter
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=56B06FD0.6000109@intel.com \
--to=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=linux-mmc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sf84@laposte.net \
--cc=shawn.lin@rock-chips.com \
--cc=slash.tmp@free.fr \
--cc=soren.brinkmann@xilinx.com \
--cc=stripathi@apm.com \
--cc=ulf.hansson@linaro.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).