This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: [ECOS] load data from floppy
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: Gary Thomas <gary at mlbassoc dot com>,eCos development <ecos-devel at sources dot redhat dot com>
- Date: 31 Jul 2003 10:23:41 +0100
- Subject: Re: [ECOS] load data from floppy
- References: <87fzlkm263.fsf@dedasys.com> <m3d6govu7p.fsf@miso.calivar.com><873chillr6.fsf@dedasys.com> <m3vfueve9h.fsf@miso.calivar.com><87el0fdcdm.fsf@dedasys.com> <m3he5b4wod.fsf@miso.calivar.com><87ispljwnh.fsf@dedasys.com> <m3vftkgv27.fsf@miso.calivar.com><1059566838.10050.1699.camel@hermes> <m365lkgkky.fsf@miso.calivar.com><1059576934.10050.1865.camel@hermes><3F282363.1070600@eCosCentric.com>
Jonathan Larmour <jifl@eCosCentric.com> writes:
> Gary Thomas wrote:
> > I think your idea of reasonable sized sectors as the basic
> > granularity
> > is the right approach. (512 bytes is OK, but maybe this should be
> > configurable) We also need to think about all the rest of the
> > "driver"
> > stuff like initialization, control, and maybe [shudder] a block cache.
>
> Some FS implementations rely on it for sane performance (as in
> performance isn't just slow but orders of magnitude slow because they
> rely on ability to instantly read back what was written) so we'll have
> to support it. But I'm sure it would be possible to have a "null"
> layer to make it optional.
>
> And similarly there's write buffering.
Caching should probably be the responsibility of the individual
filesystems. Trying to create a generic cache layer to suit every
filesystem is a big job. Just look at what they have in Linux or BSD
for this. And they have the luxury of having all the filesystems
written from scratch. Filesystems ported from elsewhere will already
have their own cache interface, which won't match ours. Also, as an
embedded system, we want to control the memory usage of individual
filesystems -- trading performance against footprint on a per-instance
basis.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts