From: Arnd Bergmann <arnd.bergmann@linaro.org>
To: Saugata Das <saugata.das@linaro.org>
Cc: "Ted Ts'o" <tytso@mit.edu>,
Artem Bityutskiy <dedekind1@gmail.com>,
Saugata Das <saugata.das@stericsson.com>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mmc@vger.kernel.org, patches@linaro.org, venkat@linaro.org
Subject: Re: [PATCH 2/3] ext4: Context support
Date: Tue, 12 Jun 2012 14:55:50 +0000 [thread overview]
Message-ID: <201206121455.50639.arnd.bergmann@linaro.org> (raw)
In-Reply-To: <CAKLKtzdLvRNFWiAV_ssFfSQFTMmgq+jHq4LNG9H70Zq9WZm5yg@mail.gmail.com>
On Tuesday 12 June 2012, Saugata Das wrote:
> > I don't think that is correct. The most obvious implementation in eMMC
> > hardware for this would be to group all data from one context to be
> > written into the same erase block, in order to reduce the amount
> > of garbage collection that needs to happen at erase time. AFAICT,
> > the main interest here is, as Ted is guessing correctly, to make sure
> > that all data which gets written into one context has roughly the
> > same life time before it gets erased or overwritten.
>
> The restriction is there on "large unit" context, which prevents
> trim/erase of the blocks till the context is active. But we do not
> enable "large unit". On non-"large unit" context, the specification
> does not restrict the trim/erase of blocks based on context.
As I said, it's not a technical limitation, but a logical conclusion
from trying to use the context ID for something useful. The only
reason to use context ID in the first place is to reduce the amount
of garbage collection in the device (improving performance and expected
life of the device), so any context ID annotations we make should be
directed at giving useful information to the device to actually do that.
Arnd
next prev parent reply other threads:[~2012-06-12 14:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 10:46 [PATCH 1/3] block: Context support Saugata Das
2012-06-11 10:46 ` [PATCH 2/3] ext4: " Saugata Das
2012-06-11 11:41 ` Artem Bityutskiy
2012-06-11 12:27 ` Ted Ts'o
2012-06-12 12:21 ` Saugata Das
2012-06-12 12:32 ` Ted Ts'o
2012-06-12 13:29 ` Arnd Bergmann
2012-06-12 14:26 ` Saugata Das
2012-06-12 14:55 ` Arnd Bergmann [this message]
2012-06-12 18:19 ` Ted Ts'o
2012-06-12 20:07 ` Arnd Bergmann
2012-06-12 20:41 ` Ted Ts'o
2012-06-13 19:44 ` Arnd Bergmann
2012-06-13 20:00 ` Ted Ts'o
2012-06-13 20:43 ` Arnd Bergmann
2012-06-14 2:07 ` Ted Ts'o
2012-06-14 16:14 ` Nicolas Pitre
2012-06-14 16:24 ` Artem Bityutskiy
2012-06-14 17:05 ` Ted Ts'o
2012-06-14 19:08 ` Nicolas Pitre
2012-06-15 9:19 ` Arnd Bergmann
2012-06-15 21:30 ` Ted Ts'o
2012-06-16 6:49 ` Arnd Bergmann
2012-06-14 21:55 ` Arnd Bergmann
2012-06-15 5:18 ` Andreas Dilger
2012-06-15 9:25 ` Arnd Bergmann
2012-06-15 9:40 ` Andreas Dilger
2012-06-15 10:54 ` Arnd Bergmann
2012-06-15 22:04 ` Ted Ts'o
2012-06-15 22:25 ` Andreas Dilger
2012-06-16 7:14 ` Arnd Bergmann
2012-06-16 7:28 ` Arnd Bergmann
2012-06-16 7:26 ` Arnd Bergmann
2012-06-16 13:49 ` Ted Ts'o
2012-06-16 17:41 ` Arnd Bergmann
2012-06-18 17:42 ` Ted Ts'o
2012-06-19 15:17 ` Arnd Bergmann
2012-06-20 15:09 ` Luca Porzio (lporzio)
2012-06-20 15:46 ` Arnd Bergmann
2012-06-22 13:29 ` Artem Bityutskiy
2012-06-22 14:07 ` Luca Porzio (lporzio)
2012-06-11 10:46 ` [PATCH 3/3] mmc: " Saugata Das
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=201206121455.50639.arnd.bergmann@linaro.org \
--to=arnd.bergmann@linaro.org \
--cc=dedekind1@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=saugata.das@linaro.org \
--cc=saugata.das@stericsson.com \
--cc=tytso@mit.edu \
--cc=venkat@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).