[ECOS] RAM FileSystem memory usage

[ECOS] RAM FileSystem memory usage

[Trenton D. Adams]

What's the overhead for the RAM filesystem driver?

Trenton D. Adams
Embedded Developer
Windows Developer
Extreme Engineering Ltd.
Calgary Alberta

Phone: 403 640 9494 ext 208
Fax:   403 640 9599

Re: [ECOS] RAM FileSystem memory usage

[Jonathan Larmour]

"Trenton D. Adams" wrote:
> 
> What's the overhead for the RAM filesystem driver?

That's quite vague. Static overhead? Overhead per file? per block? And in
what configuration?

It's probably best to try it and see IMHO :-).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

RE: [ECOS] RAM FileSystem memory usage

[Trenton D. Adams]

You're right, that was pretty vague!

What I'm wondering is this.  What's the overhead of the driver asside
from file allocation, blocks, etc.  If there's not a finite answer to
this I'll just have to test it I guess.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com 
> [ mailto:ecos-discuss-owner@sources.redhat.com ] On Behalf Of 
> Jonathan Larmour
> Sent: August 1, 2001 9:05 PM
> To: Trenton D. Adams
> Cc: 'eCos Discussion'
> Subject: Re: [ECOS] RAM FileSystem memory usage
> 
> 
> "Trenton D. Adams" wrote:
> > 
> > What's the overhead for the RAM filesystem driver?
> 
> That's quite vague. Static overhead? Overhead per file? per 
> block? And in what configuration?
> 
> It's probably best to try it and see IMHO :-).
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 
> (1223) 271062 Maybe this world is another planet's Hell 
> -Aldous Huxley || Opinions==mine
> 

Re: [ECOS] RAM FileSystem memory usage

[survey liu]

Hi,

What does this error mean?  Maybe a bug?

file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In function `hal_pc_fpe_dsr':
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: `cyg_handle_t' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: (Each undeclared identifier is reported only once
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: for each function it appears in.)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: parse error before `me'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:103: `me' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:103: warning: implicit declaration of function `cyg_thread_self'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:109: warning: implicit declaration of function `cyg_thread_get_stack_base'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:111: `cyg_addrword_t' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: At top level:
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: parse error before `hal_pc_fpe_interrupt_object'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: warning: type defaults to `int' in declaration of `hal_pc_fpe_interrupt_object'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: warning: data definition has no type or storage class
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: parse error before `hal_pc_fpe_interrupt'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: warning: type defaults to `int' in declaration of `hal_pc_fpe_interrupt'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: warning: data definition has no type or storage class
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In function `hal_platform_init':
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:170: warning: implicit declaration of function `cyg_interrupt_create'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:173: warning: implicit declaration of function `cyg_interrupt_attach'
make[1]: *** [src/plf_misc.o.d] Error 1
make[1]: Leaving directory `/cygdrive/f/liuxw_4/liuxw4_build/hal/i386/pc/v1_3_1'
make: *** [build] Error 2


david

[ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage]

[Jesper Skov]

>>>>> "survey" == survey liu <liuxw@263.net> writes:

survey> Hi, What does this error mean?  Maybe a bug?

survey> file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In
survey> function `hal_pc_fpe_dsr':
[snip]

Please check out a new version of eCos from CVS. The i386 support has
recently been overhauled - and 1.3.1 is very old.

Jesper

Re: [ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage]

[Jesper Skov]

>>>>> "survey" == survey liu <liuxw@263.net> writes:

survey> Hi, Thant you for your patient answer.

survey> I have another quest. When I checkout ecos with CVS,it always
survey> create a new folder--ecos. But when I change the repository to
survey> the new 'ecos', a error displayed " Package CYGPKG_NET:there
survey> are no version subdirectories".  Why? I am totally puzzled.

Read http://sources.redhat.com/ecos/anoncvs.html - you need the
optional net package.

Jesper

Re: [ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage]

[Jesper Skov]

>>>>> "survey" == survey liu <liuxw@263.net> writes:

survey> Hi, I have checked out all the components include eCos,net and
survey> snmp. But there is still a problem.

You probably need newer tools. Find the v2 configuration tool
somewhere on sources.redhat.com/ecos

And in the future, be sure to CC the mailing list!

Jesper

Re: [ECOS] RAM FileSystem memory usage

[Jonathan Larmour]

survey liu wrote:
> 
> Hi,
> 
> What does this error mean?  Maybe a bug?
> 
> file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In function `hal_pc_fpe_dsr':
> file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: `cyg_handle_t' undeclared (first use in this function)

Yes in as much as the PC port at that time does not work in non-kernel
configurations.

This is fixed in current anonymous CVS:
http://sources.redhat.com/ecos/anoncvs.html

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine