public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Estelle HAMMACHE <estelle.hammache@st.com>
To: Rudresh NB <getrudri@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Query
Date: Tue, 21 Dec 2004 13:42:43 +0100	[thread overview]
Message-ID: <41C81A43.C8E52F8@st.com> (raw)
In-Reply-To: 20041221120823.80642.qmail@web13205.mail.yahoo.com

Hi,
JFFS2 write pages sequentially from the start of an erase
block to the end of the block. The current
write block is in c->nextblock. The current write offset
in this block is c->nextblock->offset.
There is a write buffer (see file wbuf.c) to ensure that 
only full pages are written, even though data nodes may
overlap a page boundary. 
Data nodes may not overlap an erase block boundary: if there 
is no more room in the current block, a new (empty) block
is selected (and the page buffer is flushed in the old block
previously to writing to the new block). The new block
selection and the write address selection happen in 
nodemgmt.c (jffs2_do_reserve_space).
Does this answer your question ?
Estelle

Rudresh NB wrote:
> 
> Hi All,
>        Iam using samsung Nand flash (k9f2g08u0m). In
> that there is restriction of random page program. I
> heard that jffs2 takes care. but iam unable to find
> where exactly (In which file ) it is taken care.
> Brief explanation is appreciated.
> 
> Thanx in advance
> 
> Rgds
> NBR

  parent reply	other threads:[~2004-12-21 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 12:08 Query Rudresh NB
2004-12-21 12:19 ` Query Artem B. Bityuckiy
2004-12-21 12:42 ` Estelle HAMMACHE [this message]
2004-12-22  9:05   ` Query Rudresh NB
2004-12-22  9:26     ` Query Estelle HAMMACHE
  -- strict thread matches above, loose matches on Subject: below --
2004-06-25 13:13 query Manish RATHI

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=41C81A43.C8E52F8@st.com \
    --to=estelle.hammache@st.com \
    --cc=getrudri@yahoo.com \
    --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