From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ben Hutchings <ben@decadent.org.uk>,
Chuanxiao Dong <chuanxiao.dong@intel.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Android Kernel Team <kernel-team@android.com>,
linux-mmc@vger.kernel.org
Subject: Re: [RFC][PATCH] mmc_block: Allow more than 8 partitions per card
Date: Fri, 16 Oct 2015 15:16:06 -0400 [thread overview]
Message-ID: <56214CF6.7080105@gmail.com> (raw)
In-Reply-To: <8708065.t39NvS0r8j@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On 2015-10-16 15:08, Arnd Bergmann wrote:
> On Friday 16 October 2015 15:03:29 Austin S Hemmelgarn wrote:
>> On 2015-10-16 14:40, John Stultz wrote:
>>> From: Colin Cross <ccross@android.com>
>>>
>>> It is quite common for Android devices to utilize more
>>> then 8 partitions on internal eMMC storage. This patch,
>>> which has been carried for quite awhile in the AOSP common
>>> tree is necessary in order to support such configurations,
>>> so I wanted to submit it for consideration upstream.
>>
>> Isn't this what CONFIG_MMC_BLOCK_MINORS is for? It does limit you to
>> 256 minors total, and therefore the number of supported MMC's is equal
>> to 256/CONFIG_MMC_BLOCK_MINORS, but I've never heard of an Android
>> device with support for more than 4 MMC/SD cards (including eMMC's), and
>> I would seriously question anyone who has the need for more than 32
>> partitions on the root device for a phone/tablet/television.
>
> The 256 minor limit is really arbitrary, we should not be limited by
> that, and you should have have to decide at compile time whether you
> might need many partitions or many devices, even if we believe that
> nobody will ever need both at the same time.
I didn't mean to imply that I disagree with any of that, I was just
trying to get the point across that framing the problem this is trying
to solve in such limited terms really isn't the best idea, although I
could have gone about doing so in a better way.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-10-16 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 18:40 [RFC][PATCH] mmc_block: Allow more than 8 partitions per card John Stultz
2015-10-16 19:03 ` Austin S Hemmelgarn
2015-10-16 19:08 ` Arnd Bergmann
2015-10-16 19:16 ` Austin S Hemmelgarn [this message]
2015-10-16 19:31 ` John Stultz
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=56214CF6.7080105@gmail.com \
--to=ahferroin7@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=ben@decadent.org.uk \
--cc=ccross@android.com \
--cc=chuanxiao.dong@intel.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.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