public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] jffs2 write in 4kB blocks over the network?
Date: Mon, 07 Apr 2008 13:34:00 -0000	[thread overview]
Message-ID: <47FA213E.3070101@mlbassoc.com> (raw)
In-Reply-To: <20080407151713.08e665ee@kingfisher.sec.intern.logix-tt.com>

Markus Schaber wrote:
> Hi, Jürgen,
> 
> Jürgen Lambrecht <J.Lambrecht@televic.com> wrote:
> 
>> 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) ?
> 
> Besides what Jürgen wrote, it also depends on how your FTP program
> buffers, which parts it writes in a single write call, and when it
> syncs/flushes buffers.

It still doesn't matter because the file system and/or JFFS2 will
be buffering it to suit their needs.

-- 
------------------------------------------------------------
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 13:28 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
2008-04-07 13:26 ` Markus Schaber
2008-04-07 13:34   ` Gary Thomas [this message]
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=47FA213E.3070101@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=schabi@logix-tt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).