From: David Woodhouse <dwmw2@infradead.org>
To: "Paul Lai" <paul.lai@intransa.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 and flash sectors
Date: Thu, 28 Feb 2002 18:42:49 +0000 [thread overview]
Message-ID: <4190.1014921769@redhat.com> (raw)
In-Reply-To: <EA23924D8B48774F889C7733226B28E80E7DBA@exalane.intransa.com>
paul.lai@intransa.com said:
> How cognizant of flash sectors is jffs2?
Very.
> Will an inode and it's data cross flash sector boundaries?
No single node (log entry) will cross sector boundary. An inode may have
nodes in any sectors though.
> Or will jffs2 align them to fit within and start them on flash sector
> boundaries?
http://sources.redhat.com/jffs2/jffs2.pdf
--
dwmw2
next prev parent reply other threads:[~2002-02-28 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 17:39 jffs2 and flash sectors Paul Lai
2002-02-28 18:42 ` David Woodhouse [this message]
2002-03-01 3:58 ` New Release Michael Michael
2002-03-01 9:52 ` David Woodhouse
2002-03-02 6:56 ` Looking for NAND emulation driver Charles Manning
2002-03-02 8:14 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 18:43 jffs2 and flash sectors Paul Lai
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=4190.1014921769@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=paul.lai@intransa.com \
/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