* [ECOS] RAM FileSystem memory usage
@ 2001-08-01 15:13 Trenton D. Adams
2001-08-01 20:07 ` Jonathan Larmour
0 siblings, 1 reply; 8+ messages in thread
From: Trenton D. Adams @ 2001-08-01 15:13 UTC (permalink / raw)
To: 'eCos Discussion'
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ECOS] RAM FileSystem memory usage
2001-08-01 15:13 [ECOS] RAM FileSystem memory usage Trenton D. Adams
@ 2001-08-01 20:07 ` Jonathan Larmour
2001-08-01 21:24 ` Trenton D. Adams
0 siblings, 1 reply; 8+ messages in thread
From: Jonathan Larmour @ 2001-08-01 20:07 UTC (permalink / raw)
To: Trenton D. Adams; +Cc: 'eCos Discussion'
"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
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: [ECOS] RAM FileSystem memory usage
2001-08-01 20:07 ` Jonathan Larmour
@ 2001-08-01 21:24 ` Trenton D. Adams
2001-08-01 22:33 ` survey liu
0 siblings, 1 reply; 8+ messages in thread
From: Trenton D. Adams @ 2001-08-01 21:24 UTC (permalink / raw)
To: 'Jonathan Larmour', 'Trenton D. Adams'
Cc: 'eCos Discussion'
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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ECOS] RAM FileSystem memory usage
2001-08-01 21:24 ` Trenton D. Adams
@ 2001-08-01 22:33 ` survey liu
2001-08-02 0:44 ` [ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage] Jesper Skov
2001-08-02 10:03 ` [ECOS] RAM FileSystem memory usage Jonathan Larmour
0 siblings, 2 replies; 8+ messages in thread
From: survey liu @ 2001-08-01 22:33 UTC (permalink / raw)
To: Trenton D. Adams; +Cc: 'eCos Discussion'
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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2001-08-02 10:03 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-01 15:13 [ECOS] RAM FileSystem memory usage Trenton D. Adams
2001-08-01 20:07 ` Jonathan Larmour
2001-08-01 21:24 ` Trenton D. Adams
2001-08-01 22:33 ` survey liu
2001-08-02 0:44 ` [ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage] Jesper Skov
[not found] ` <007e01c11b33$dffa4f10$fca210ac@utszrtsurveyl>
2001-08-02 2:24 ` Jesper Skov
[not found] ` <001401c11b4a$81af3e40$fca210ac@utszrtsurveyl>
2001-08-02 5:04 ` Jesper Skov
2001-08-02 10:03 ` [ECOS] RAM FileSystem memory usage Jonathan Larmour
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).