public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Nikhil" <nikhils@cdac.in>
To: <linux-mtd@lists.infradead.org>
Subject: Question regading Cleanmarker.
Date: Fri, 13 Jan 2006 20:26:07 +0530 (IST)	[thread overview]
Message-ID: <twig.1137164167.21280@cdac.in> (raw)


Hi all,

I am analysing the jffs2 methodology for updating the flash memory. I
understand that the jffs2_sb_info maintains three list i.e free_list,
clean_list and dirty_list.

the garbage collector acts on the blocks on the dirty_list and on erasing
those blocks writes a CLEANMARKER to the first 12 bytes indicating
succesful erase and move the block from dirty_list to free_list.

So all the blocks in the free_list are empty with first twelve bytes
having a CLEANMARKER. Whenever some node has to be written on the flash, a
block from the free_list is picked and written.

whether it will overwrite the CLEANMARKER bytes... if so then it has to
perform erase of the whole block again...

else the block is appended after the CLEANMARKER bytes... if so, then
after some time when this block moves from clean_list to dirty_list (by
some updations on the file data or else) how will the garbage collector
identify the block as clean/unclean as the the CLEANMARKER will be
present. 

whether the garbage collector neglects this CLEANMARKER when is it getting
updated or removed? else after some point of time, all the eraseblocks
will have a CLEANMARKER which will defeat the basic purpose of having a
CLEANMARKER.  
 
there is one more query about delayed write. What is the size of the
buffer which gets written on the flash? is it the page size or the erase
block size or is it a function of time?

Can you help in clearing my doubt?

-- 
Thanks & Regards

Nikhil Shirodkar
Project Engineer
NISG, CDAC

             reply	other threads:[~2006-01-13 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 14:56 Nikhil [this message]
2006-01-13 16:19 ` Question regading Cleanmarker Josh Boyer

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=twig.1137164167.21280@cdac.in \
    --to=nikhils@cdac.in \
    --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