From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anatolij Gustschin <agust@denx.de>
Cc: MTD list <linux-mtd@lists.infradead.org>
Subject: [PATCH v3 4/7] UBI: incorporate LEB offset information
Date: Tue, 8 Mar 2011 10:32:45 +0200 [thread overview]
Message-ID: <1299573168-27760-5-git-send-email-dedekind1@gmail.com> (raw)
In-Reply-To: <1299573168-27760-1-git-send-email-dedekind1@gmail.com>
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Incorporate the LEB offset information into UBIFS. We'll use this
information in one of the next patches to figure out what are the
max. write size offsets relative to the PEB. So this patch is just
a preparation.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
---
fs/ubifs/super.c | 1 +
fs/ubifs/ubifs.h | 3 +++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
index 6a38174..c20c6d2 100644
--- a/fs/ubifs/super.c
+++ b/fs/ubifs/super.c
@@ -512,6 +512,7 @@ static int init_constants_early(struct ubifs_info *c)
c->leb_cnt = c->vi.size;
c->leb_size = c->vi.usable_leb_size;
+ c->leb_start = c->di.leb_start;
c->half_leb_size = c->leb_size / 2;
c->min_io_size = c->di.min_io_size;
c->min_io_shift = fls(c->min_io_size) - 1;
diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
index 8b51949..942c1d3 100644
--- a/fs/ubifs/ubifs.h
+++ b/fs/ubifs/ubifs.h
@@ -1028,6 +1028,8 @@ struct ubifs_debug_info;
* time (MTD write buffer size)
* @max_write_shift: number of bits in @max_write_size minus one
* @leb_size: logical eraseblock size in bytes
+ * @leb_start: starting offset of logical eraseblocks within physical
+ * eraseblocks
* @half_leb_size: half LEB size
* @idx_leb_size: how many bytes of an LEB are effectively available when it is
* used to store indexing nodes (@leb_size - @max_idx_node_sz)
@@ -1276,6 +1278,7 @@ struct ubifs_info {
int max_write_size;
int max_write_shift;
int leb_size;
+ int leb_start;
int half_leb_size;
int idx_leb_size;
int leb_cnt;
--
1.7.2.3
next prev parent reply other threads:[~2011-03-08 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 8:32 [PATCH v3 0/7] UBIFS: fix recovery on CFI NOR Artem Bityutskiy
2011-03-08 8:32 ` [PATCH v3 1/7] UBI: incorporate maximum write size Artem Bityutskiy
2011-03-08 8:32 ` [PATCH v3 2/7] UBI: provide LEB offset information Artem Bityutskiy
2011-03-08 8:32 ` [PATCH v3 3/7] UBIFS: incorporate maximum write size Artem Bityutskiy
2011-03-08 8:32 ` Artem Bityutskiy [this message]
2011-03-08 8:32 ` [PATCH v3 5/7] UBIFS: introduce write-buffer size field Artem Bityutskiy
2011-03-08 8:32 ` [PATCH v3 6/7] UBIFS: use max_write_size for write-buffers Artem Bityutskiy
2011-03-08 8:32 ` [PATCH v3 7/7] UBIFS: use max_write_size during recovery Artem Bityutskiy
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=1299573168-27760-5-git-send-email-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=agust@denx.de \
--cc=linux-mtd@lists.infradead.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