From: David Woodhouse <dwmw2@infradead.org>
To: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 internals question
Date: Thu, 14 Aug 2003 13:56:17 +0100 [thread overview]
Message-ID: <1060865777.3152.79.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <3F3B81FD.1010205@elsoft.ch>
On Thu, 2003-08-14 at 13:35, "David Müller (ELSOFT AG)" wrote:
> Sorry, i was talking about block boundary, not page boundary. Or is it
> just a typo?
Oh, sorry. We'll not read over _logical_ eraseblock boundaries but on
large chips we may artificially increase the eraseblock size to be 2* or
4* the physical eraseblock size, to reduce the number of 'struct
jffs2_eraseblock' we have to allocate. In that case, yes, we'll be
reading across eraseblock boundaries.
--
dwmw2
prev parent reply other threads:[~2003-08-14 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 11:42 JFFS2 internals question "David Müller (ELSOFT AG)"
2003-08-14 11:47 ` David Woodhouse
2003-08-14 12:15 ` "David Müller (ELSOFT AG)"
2003-08-14 12:21 ` David Woodhouse
2003-08-14 12:34 ` jasmine
2003-08-14 12:35 ` "David Müller (ELSOFT AG)"
2003-08-14 12:56 ` David Woodhouse [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=1060865777.3152.79.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=d.mueller@elsoft.ch \
--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