Subject: Re: tmpfs: Internal representation of data
To: Julio M. Merino Vidal <jmmv84@gmail.com>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 07/19/2005 18:12:21
--5p8PegU4iirBW1oA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 19, 2005 at 10:00:04PM +0200, Julio M. Merino Vidal wrote:
> On 7/19/05, Matt Thomas <matt@3am-software.com> wrote:
> > Julio M. Merino Vidal wrote:
> >=20
> > One thing you may want to consider is that eventually that the tmpfs
> > maybe replace the current md-root mechanism but using an external tool
> > to write a tmpfs into a kernel.
>=20
> Good idea.
>=20
> > > Suppressing the former (merging it with directory contents,
> > > thus becoming something like the FAT) means that
> > > implementing hard links becomes very complex, so the
> > > separation is worth it.
> >=20
> > Directories are just files and should be kept in the format returned
> > by getdents(2).
>=20
> Aha.

Try getdirents for now. Later on we can play with this. You can also=20
"borrow" code from the ufs lookup code.

> > I would use pools, not malloc/free.
>=20
> Oh.  I wasn't aware of these "pools", but as you say it, they seem
> to be The Solution.  I'll take a look at them.

Yes, please do.

Take care,

Bill

--5p8PegU4iirBW1oA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFC3aT1Wz+3JHUci9cRAi6VAJ43C6J2sYn4l6NzhmznTh9cxpxgTACgk1Z0
C5IDrcavXejrwObrbg6dPvI=
=Rm+r
-----END PGP SIGNATURE-----

--5p8PegU4iirBW1oA--