On Mon, Jun 05, 2000 at 04:57:30PM -0700, Eric Cox wrote:
> clemensF wrote:
> >
> > > David Dyer-Bennet:
> >
> > > > identical program invocations get to run their own copy of the program
> > > > text.
> > >
> > > I don't believe this last bit is the case. It's clearly not the case
> > > on Linux, anyway, as displayed by the various size numbers in 'top'.
> >
> > but linux processes don't share one copy of, say, top, when it is called
> > twice by different users, do they?
Yes they do.
> I'm pretty sure they do. Since programs can't modify their own
> code space on a Linux system, there's really no reason to have
> multiple images of any given program code in memory. Multiple
> stacks, heaps, and sets of file descriptors, etc, but not program
> code.
Correct. Same for library code.
> Your system is probably just thrashing with higher concurrencies
> because it's swapping out chunks of the dynamic data of all those
> processes...
Yes, dynamic data ofcourse still needs room in memory.
Greetz, Peter.
--
[EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
