From: "Trenton D. Adams" <trent.nospam@telusplanet.net>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>,
"'Trenton D. Adams'" <tadams@extremeeng.com>
Cc: "'eCos Discussion'" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] RAM FileSystem memory usage
Date: Wed, 01 Aug 2001 21:24:00 -0000 [thread overview]
Message-ID: <000001c11b0b$013f4b40$0307a8c0@ab.hsia.telus.net> (raw)
In-Reply-To: <3B68C354.C0EC19CA@redhat.com>
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
>
next prev parent reply other threads:[~2001-08-01 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 15:13 Trenton D. Adams
2001-08-01 20:07 ` Jonathan Larmour
2001-08-01 21:24 ` Trenton D. Adams [this message]
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
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='000001c11b0b$013f4b40$0307a8c0@ab.hsia.telus.net' \
--to=trent.nospam@telusplanet.net \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@redhat.com \
--cc=tadams@extremeeng.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).