From: Adrian Hunter <adrian.hunter@nokia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Kyungmin Park <kmpark@infradead.org>,
Madhusudhan Chikkature <madhu.cr@ti.com>,
linux-mmc Mailing List <linux-mmc@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH V3 1/5] mmc: Add erase, secure erase, trim and secure trim operations
Date: Thu, 01 Jul 2010 13:49:32 +0300 [thread overview]
Message-ID: <4C2C72BC.1050207@nokia.com> (raw)
In-Reply-To: <20100630152144.3822fe6b.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 24 Jun 2010 11:44:00 +0300
> Adrian Hunter <adrian.hunter@nokia.com> wrote:
>
>> SD/MMC cards tend to support an erase operation. In addition,
>> eMMC v4.4 cards can support secure erase, trim and secure trim
>> operations that are all variants of the basic erase command.
>
> The patch proposes a new userspace interface via sysfs, yes?
,
Just two read-only values
>
> Please fully describe that interface and its operation in the
> changelog. It'd also be nice to add permanent documentation for it.
>
OK
>>From reading the code, it appears that erase_size and
> preferred_erase_size have units in bytes. But users shouldn't need to
> read the code to find that out. What are the alignemnt and size
> requirements on these? What is their position in /sys? What do they
> actually *do* and what is the difference between them?
>
> etetera. People want to review this code and other people actually
> want to use it. I'm not sure that I want to try to review this code
> when nobody's told me what interface it implements and how it's
> supposed to work. Seems that whoever implemented BLKDISCARD didn't
> want anyone to use it either. Sigh.
>
>
> All of mmc core appears to use 32-bit quantities to represent sectors,
> yes? Why didn't it use sector_t? What are the implications of this?
SD/MMC addressing uses 32-bit values. There is a known 2TB limit for
SD/MMC cards. As cards are only just getting to 64GB, that limit is
some way off, and it is not clear NAND technology can get there in
a SD/MMC package anyway.
I don't know why sector_t is not used. I guess it would complicate doing
division since it can be 64-bit.
The implications are minimal. In the unlikely event SD/MMC cards ever
exceed 2TB some changes will be needed, but the standard would have to
change to allow that first.
next prev parent reply other threads:[~2010-07-01 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 8:43 [PATCH V3 0/5] Add MMC erase and secure erase V3 Adrian Hunter
2010-06-24 8:44 ` [PATCH V3 1/5] mmc: Add erase, secure erase, trim and secure trim operations Adrian Hunter
2010-06-30 22:21 ` Andrew Morton
2010-07-01 10:49 ` Adrian Hunter [this message]
2010-06-24 8:44 ` [PATCH V3 2/5] mmc_block: Add discard support Adrian Hunter
2010-06-24 8:44 ` [PATCH V3 3/5] omap_hsmmc: Add erase capability Adrian Hunter
2010-06-24 8:44 ` [PATCH V3 4/5] block: Add secure discard Adrian Hunter
2010-06-30 22:09 ` Andrew Morton
2010-07-01 10:18 ` Adrian Hunter
2010-06-24 8:44 ` [PATCH V3 5/5] mmc_block: Add support for " 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=4C2C72BC.1050207@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kmpark@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=madhu.cr@ti.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).