public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] jffs2 write in 4kB blocks over the network?
Date: Mon, 07 Apr 2008 13:08:00 -0000	[thread overview]
Message-ID: <47FA10F8.8080602@mlbassoc.com> (raw)
In-Reply-To: <47F9DD83.30800@televic.com>

Jürgen Lambrecht wrote:
> Hello,
> 
> the default block size in jffs2 is 4kB. But with FTP, packets have at 
> most 1448 B payload.
> If I put a file of 12kB, is the file then put in 3 nodes if 4kB, or is 
> it put in 9 nodes (because FTP uses 9 packets) ?

JFFS2 will pack your data in the most efficient way into your
actual FLASH blocks.  In fact, depending on configuration and
settings, it will even compress it along the way, so you've
no real idea how many FLASH blocks a given set of data will
require (except that it will be less than the actual data
size divided by the FLASH block size - compression is never
used if it causes the data to grow).

The fact that your incoming data via FTP or whatever comes
in smaller chunks is irrelevant - writes are buffered as
needed.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-04-07 12:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 10:48 Jürgen Lambrecht
2008-04-07 13:08 ` Gary Thomas [this message]
2008-04-07 13:26 ` Markus Schaber
2008-04-07 13:34   ` Gary Thomas
2008-04-07 13:40     ` Markus Schaber
2008-04-07 14:37       ` Gary Thomas
2008-04-07 14:55         ` Jürgen Lambrecht

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=47FA10F8.8080602@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=J.Lambrecht@televic.com \
    --cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).