public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: Sergei Sharonov <sergei.sharonov@halliburton.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mounting jffs2
Date: Thu, 14 Apr 2005 19:18:03 +0400	[thread overview]
Message-ID: <425E89AB.9030307@yandex.ru> (raw)
In-Reply-To: <loom.20050414T151238-645@post.gmane.org>

Sergei Sharonov wrote:
> Sorry, I meant two partitions. (blocks is sense of /dev/mtdblock ;)
It's hard to answer, I don't know your task and requirements.

> I'll run a test with 10x20 MByte files and post results.
It would be nice. If you provide mount time speeds with depending on how 
many data is placed on flash, it would be nice. I then add these numbers 
to the JFFS3 document for reference (the brief description of your 
system would be useful as well).

> What would be a time frame for a stable JFFS3 solution assuming there is a 
> support?
Design is even not ready yet. But I'd say it could take 4-6 months
depending on requirements, fetures to implement, people involved, etc.

> Got 32 MB, can probably go to 64 MB. Will that be sufficient to support 
> 256 MB NAND assuming 1 kB writes? BTW, does it make sense to increase write 
> size above 1 page (2 kB). I understood from previous discussions that jffs2 
> will split it on a page boundary anyway?
No. JFFS (even not JFFS2, but the Linux Page Cache) split on *RAM* page 
boundary which is PAGE_SIZE bytes big and is, as a rule, 4KiB. And 4KiB 
is a JFFS2's lovely size :-)

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

  reply	other threads:[~2005-04-14 15:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 13:25 mounting jffs2 Sergei Sharonov
2005-04-13 13:50 ` Artem B. Bityuckiy
2005-04-13 14:22   ` Sergei Sharonov
2005-04-13 15:02     ` Artem B. Bityuckiy
2005-04-13 17:51       ` Sergei Sharonov
2005-04-14  8:41         ` Artem B. Bityuckiy
2005-04-14 12:39           ` Sergei Sharonov
2005-04-14 13:11             ` Artem B. Bityuckiy
2005-04-14 14:15               ` Sergei Sharonov
2005-04-14 15:18                 ` Artem B. Bityuckiy [this message]
2005-04-13 15:18     ` Artem B. Bityuckiy
2005-04-14 20:39   ` Sergei Sharonov
2005-04-14  9:01 ` Ferenc Havasi
2005-04-14  9:15   ` Artem B. Bityuckiy
2005-04-20 14:59     ` Sergei Sharonov
2005-04-20 15:20       ` Artem B. Bityuckiy
2005-04-20 16:34         ` Sergei Sharonov
2005-04-21  7:48       ` Artem B. Bityuckiy
2005-04-21 14:30       ` Ferenc Havasi
2005-04-21 15:31         ` Artem B. Bityuckiy
2005-04-26 13:35           ` Zoltan Sogor
2005-04-26 13:51             ` Artem B. Bityuckiy
2005-04-27  9:39               ` Zoltan Sogor
2005-04-21 15:34         ` Sergei Sharonov

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=425E89AB.9030307@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sergei.sharonov@halliburton.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