lkml.org 
[lkml]   [2001]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [Acpi] Re: ACPI fundamental locking problems
Date
On Saturday 07 July 2001 15:50, Jeff Garzik wrote:
> Eugene Crosser wrote:
> > In article
> > <Pine.GSO.4.21.0107070727030.24836-100000@weyl.math.psu.edu>,
> >
> > Alexander Viro <viro@math.psu.edu> writes:
> > >> Doesn't the approach "treat a chunk of data built into bzImage
> > >> as populated ramfs" look cleaner? No need to fiddle with tar
> > >> format, no copying data from place to place.
> > >
> > > What the hell _is_ "populated ramfs"? The thing doesn't live in
> > > array of blocks. Its directory structure consists of a bunch of
> > > dentries.
> >
> > I am stupid. But the point still stays: having an image of
> > pre-populated filesystem (some other than ramfs) that you only need
> > to load into RAM seems more sutable than parsing tar format. Maybe
> > (probably) I am missing something.
>
> Yeah -- we build all this stuff dynamically. struct file, struct
> inode, etc. You could store them on disk as they would be
> represented in memory, but this would be incredibly inefficient
> because of all the runtime structures unnecessary on disk, and
> because of all the fixups and checks you would have to perform on the
> data in the images after they magically appear in memory.

Not to mention internal fragmentation.

> Reading a tarball is the distillation of what you describe into
> efficient form :)

/me downloads tar file definition

Um, gnu tar or posix tar? or some new, improved tar?

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:56    [W:0.130 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site