Re: size of files in /proc

Aaron M. Ucko (amu@mit.edu)
19 May 1998 18:23:06 -0500


Kevin Lentin <kevinl@cs.monash.edu.au> writes:

> On Sat, May 16, 1998 at 11:00:28AM -0400, Mike A. Harris wrote:
> >
> > And it isn't about to change at runtime either. That is the size
> > of installed memory. I've yet to see a single person
> > successfully insert or remove a SIMM/DIMM while a machine was
> > running. If they did, and it was successful, the linux code will
> > update the filesize. ;o)

I'm almost tempted to obtain an old 386 and borrow a video camera to
disprove this claim. :-)

> And even if you could resize memory, kcore could update it's size. The
> reason kcore shows its size is that the size is known. And it's also
> relevant! For most of the text files in /proc, you'd have to actually call
> the 'read' function to determine the size each time a readdir was done.
> Sounds like a very wasteful pursuit to me.

stat, not readdir --- a dirent just contains a name and an inode
number --- but yeah.

-- 
Aaron M. Ucko <amu@mit.edu> (finger amu@monk.mit.edu) [Stark raving sane]

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu