linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd.bergmann@linaro.org>
To: "Luca Porzio (lporzio)" <lporzio@micron.com>
Cc: "Ted Ts'o" <tytso@mit.edu>,
	Alex Lemberg <Alex.Lemberg@sandisk.com>,
	HYOJIN JEONG <syr.jeong@samsung.com>,
	Saugata Das <saugata.das@linaro.org>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Saugata Das <saugata.das@stericsson.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"patches@linaro.org" <patches@linaro.org>,
	"venkat@linaro.org" <venkat@linaro.org>
Subject: Re: [PATCH 2/3] ext4: Context support
Date: Wed, 20 Jun 2012 15:46:27 +0000	[thread overview]
Message-ID: <201206201546.27362.arnd.bergmann@linaro.org> (raw)
In-Reply-To: <26E7A31274623843B0E8CF86148BFE32779D94DD@NTXAVZMBX04.azit.micron.com>

On Wednesday 20 June 2012, Luca Porzio (lporzio) wrote:
> > > > * We can only start the large unit at the start of an erase block. If
> > > >   we unmount the drive and later continue writing, it has to continue
> > > >   without the large-unit flag at first until we hit an erase block
> > > >   boundary.
> > >
> > > My assumption was that when you umount the drive, the file system
> > > would close all of the contexts.
> > 
> > Yes, makes sense. This is probably required to ensure that the data
> > has made to the drive, at least for the large contexts, but it is
> > definitely required for housekeeping of contexts if we manage them
> > from the block layer.
> > 
> 
> One comment here, large unit contexts (according to spec) are not bounded
> to erase blocks. They can span one or more blocks, actually they are not
> related to block size at all (just virtual page size of the device which
> can be read from the EXT_CSD configuration registers for eMMC).

Well, when I say erase block, I really mean the "large unit", which is some
multiple of entire megabytes, because the only reasonable way to use this
is to define this to the size of the erase block or a very small multiple
of that. When detecting the "erase block size" of an eMMC, we should report
the smallest multiple of the ERASE_GPR_SIZE, HC_ERASE_GRP_SIZE and 
LARGE_UNIT_SIZE_M1.

	Arnd

  reply	other threads:[~2012-06-20 15:46 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
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 [this message]
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=201206201546.27362.arnd.bergmann@linaro.org \
    --to=arnd.bergmann@linaro.org \
    --cc=Alex.Lemberg@sandisk.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lporzio@micron.com \
    --cc=patches@linaro.org \
    --cc=saugata.das@linaro.org \
    --cc=saugata.das@stericsson.com \
    --cc=syr.jeong@samsung.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).