public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Vincent Catros <Vincent.Catros@elios-informatique.fr>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: RE : RE : [ECOS] Is JFFS2 thread-safe?
Date: Thu, 27 Nov 2003 10:24:00 -0000	[thread overview]
Message-ID: <1069928653.18076.26.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <000701c3b4cd$b07c5720$7407a8c0@figuier>

On Thu, 2003-11-27 at 11:03 +0100, Vincent Catros wrote:
> Thanks David,
> 
> This is clear for me now.

Good.

In answer to your earlier question about chmod/chown -- they're trivial
to implement. JFFS2 needs to keep track of modes and ownership
internally (in its struct _inode) so that it doesn't corrupt them when
modifying a file system shared with Linux. They should already be
returned by stat(), and the only barrier to allowing you to _change_
modes or ownership from your application is the lack of suitable API for
such purpose. I don't really want to abuse jffs2_setinfo().

The TODO list for JFFS2/eCos is now as follows. I'm hoping someone with
more eCos-clue will pick up some of this:

 - Fill in the skeleton gcthread.c so it actually does something.

 - Check and possibly fix locking of icache mangling in fs-ecos.c

 - Check that os-ecos.h defines 'spin_lock()' to something appropriate.

 - Fix unmount of root file system after chdir().

 - Fix atomicity of renames. Why was the unlink added before rename?

 - Further cleanup -- should the functions in dir-ecos.c take 'struct
   dirsearch' instead of various components thereof, or should each of
   those functions just be moved inside its only caller in fs-ecos.c?

 - Improve mount time by using pointer directly into flash chip instead
   of jffs2_flash_read() for the initial scan -- look at the #ifdef
   __ECOS bit in scan.c for details.

 - Reduce memory usage. There are fields marked for possible removal in
   struct _inode, and there's the __totlen field in struct
   jffs2_raw_node_ref as discussed recently.

Sort of separate, and I have a hacked-up mostly working version already:

 - Make fileio package not gratuitously include kernel header files.

 - Add up RedBoot fileio support so RedBoot can read/write JFFS2.

-- 
dwmw2



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

  reply	other threads:[~2003-11-27 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  9:15 Vincent Catros
2003-11-27  0:27 ` David Woodhouse
2003-11-27  9:12   ` [ECOS] RE : " Vincent Catros
2003-11-27  9:36     ` [ECOS] " David Woodhouse
2003-11-27 10:00       ` [ECOS] RE : " Vincent Catros
2003-11-27 10:24         ` David Woodhouse [this message]
2003-11-28 11:14     ` [ECOS] " David Woodhouse
     [not found]       ` <1070018876.10048.35.camel@hades.cambridge.redhat.com>
2003-11-28 16:09         ` David Woodhouse
2003-11-29 14:54           ` Gary Thomas
2003-11-29 15:46             ` David Woodhouse
2003-11-29 15:47           ` Nick Garnett
2003-11-29 19:40             ` David Woodhouse
2003-11-27 17:02   ` Vincent Catros
2003-11-28 11:09     ` [ECOS] " David Woodhouse

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=1069928653.18076.26.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=Vincent.Catros@elios-informatique.fr \
    --cc=ecos-discuss@sources.redhat.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).