From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>
Cc: "dedekind1@gmail.com" <dedekind1@gmail.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"baruch@tkos.co.il" <baruch@tkos.co.il>,
"asierra@xes-inc.com" <asierra@xes-inc.com>,
"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
"gsi@denx.de" <gsi@denx.de>, "richard@nod.at" <richard@nod.at>,
"David Woodhouse" <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Frank Liu 刘群 (frankliu)" <frankliu@micron.com>,
"Andrea Scian" <rnd4@dave-tech.it>,
"Peter Pan 潘柏宏 (peterpan)" <peterpan@micron.com>,
"Karl Zhang 张双锣 (karlzhang)" <karlzhang@micron.com>,
"Iwo Mergler" <Iwo.Mergler@netcommwireless.com>,
"Jeff Lauruhn (jlauruhn)" <jlauruhn@micron.com>,
"Stefan Roese" <sr@denx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/9] drivers:mtd:ubi:add metadata struct for UBI bakvol
Date: Mon, 28 Sep 2015 12:06:51 +0200 [thread overview]
Message-ID: <20150928120651.5c55317d@bbrezillon> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6310BF4CEE1@NTXXIAMBX02.xacn.micron.com>
On Mon, 28 Sep 2015 07:02:42 +0000
Bean Huo 霍斌斌 (beanhuo) <beanhuo@micron.com> wrote:
> Add metadata struct for UBI bakvol.
> Currently , bakvol reserves 20 PEBs for internal log volume.
> Shares wear-leveling operation with ubi.
>
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
> ---
> drivers/mtd/ubi/ubi-media.h | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
[...]
>
> @@ -325,6 +339,32 @@ struct ubi_vid_hdr {
> #define UBI_VTBL_RECORD_SIZE_CRC (UBI_VTBL_RECORD_SIZE - sizeof(__be32))
>
> /**
> + * struct ubi_bkblk_info - the information for one backup block .
> + * @pbn: physical block number
> + * @lbn: logic block number
> + * @plane: this block belongs to which plane
> + * @pgnum: the page number (lower page) that can be programmed last time
> + */
I'm not sure to understand what those fields are used for, but I guess
I'll understand it while reviewing the following patches.
> +struct ubi_bkblk_info {
> + __be32 pbn;
> + __be32 lbn;
> + __u8 plane;
> + __be32 pgnum;
> + struct list_head node;
> +};
You're mixing runtime and storage representation: node has nothing to
do here.
> +
> +/**
> + * struct ubi_bkblk_tbl - a table for backup blocks.
> + * @volume_built: indicate if backup volume be initted
> + * @bcount_of_plane: block count that has bee applied for corresponding plane
> + */
> +struct ubi_bkblk_tbl {
> + __u8 volume_built;
> + __be32 bcount_of_plane[2];
> + struct list_head head;
> +};
Ditto.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2015-09-28 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 7:02 [PATCH 3/9] drivers:mtd:ubi:add metadata struct for UBI bakvol Bean Huo 霍斌斌 (beanhuo)
2015-09-28 10:06 ` Boris Brezillon [this message]
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=20150928120651.5c55317d@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=Iwo.Mergler@netcommwireless.com \
--cc=adrian.hunter@intel.com \
--cc=asierra@xes-inc.com \
--cc=baruch@tkos.co.il \
--cc=beanhuo@micron.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frankliu@micron.com \
--cc=gsi@denx.de \
--cc=guz.fnst@cn.fujitsu.com \
--cc=jlauruhn@micron.com \
--cc=karlzhang@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=peterpan@micron.com \
--cc=richard@nod.at \
--cc=rnd4@dave-tech.it \
--cc=sr@denx.de \
/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).