All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Peter Menzebach <pm-mtd@mw-itcon.de>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Minimum/optimal sector_size for jffs2
Date: Fri, 23 Sep 2005 14:05:46 +0400	[thread overview]
Message-ID: <4333D37A.1020900@yandex.ru> (raw)
In-Reply-To: <4333D014.8000809@mw-itcon.de>

Peter Menzebach wrote:
> Hi,
> since my grep through the source code was not successful:
> Is there a minimum possible jffs2_sb_info.sector_size and somewhere a 
> definition?
There is probably no minimum value, but not because it doesn't matter, 
just because nobody cared adding a check.

> Is there somewhat like an optimal sector_size?
Not sure about optimal, probably yes. Consider the following aspects:

1. There is an array (c->blocks[]) with one element per eraseblock. The 
smaller is yur eraseblock - the larger is the array.

2. The eraseblock size cannot be less then PAGE_SIZE + sizeof(struct 
jffs2_raw_inode). PAGE_SIZE is mostly 4096 bytes.

3. The space at the end of eraseblock is not used if there are less then 
JFFS2_MIN_DATA_LEN bytes, or if the node beinf written does not fit that 
space. So, the smaller is the eraseblock, the more space is wasted.

> I have here a device (dataflash), which has a very small
> erase/write page size (1056 bytes).
Err, AFAIR, I explained why you cannot use 1056 bytes eraseblocks... It 
is simply too small.

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

  reply	other threads:[~2005-09-23 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  9:51 Minimum/optimal sector_size for jffs2 Peter Menzebach
2005-09-23 10:05 ` Artem B. Bityutskiy [this message]
2005-09-23 11:30   ` Peter Menzebach
2005-09-25 15:15     ` Jörn Engel
2005-09-26  8:56       ` Artem B. Bityutskiy
2005-09-27 14:59     ` Artem B. Bityutskiy
2005-09-27 17:54       ` Peter Menzebach

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=4333D37A.1020900@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pm-mtd@mw-itcon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.