> > > 2. Add in code to update the data structure linkages (next pointers).
> > > This would still use the existing algorithms for using indexes into
> > > the allocated array and would still expect contiguous space. But the
> > > beginnings of the linked lists would be established.
> > > 3. Finish changing the code to remove any contiguous space requirements.
> > > All linked list work and use of worker_score pointers would be
> > > implemented here. This is the first big step.
> >
> > This is not going to accomplish what we want (at least I don;t see it). If
> > the parent allocates shared storage after the children have been forked, the
> > pointers to this shared storage area are not necessarily the same across the
> > child processes. In other words, if the parent allocates shared storage,
> > the pointer to that storage will not be the same value across the child
> > processes. Dean pointed this out on the apr-dev list.
> >
> > Bill
>
> For the time being, the shared storage will still be allocated in a "big
> chunk" up front (until we can figure out how to allocate and free smaller
> chunks). We will unfortunately still be allocating more than is usually
> needed, but will now be able to avoid allocating the (bigger) part related
> to mod_status if it isn't loaded. So overall it should usually be a
> memory savings.
How does that work if mod_status is later enabled by modifying the config
file? Won't it all of a sudden break?
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
