Re: New SHM server broken?

  Corey Wrote:
> Why not just load the registry into a disk based memory space I'm sure
> it does not get paged that much to warrant it being in SHM at all.
Well,  the point with Shm was not about paging, but preventing context
switches. Without Shm, for every registry lookup, a request to the
server is made, the winserver process had to run, the request looked up,
the reply sent back and control returns to the original wine process.
This takes relatively much time. 
With Shm, wine processes can acces the registry values themselves,
saving 2 context switches. At least, this is how I believe it is. Am I
right?
													
  Gov Wrote:
> Is that a registry that comes from a real Windows install, or one that
> came from WineX with many many games loaded?
Real windows install, plus some games installed.

> Regardless, the ShmServer does need to handle a situation like this
> gracefully and not crash, etc.  Perhaps we can disable Shm mode on
> startup if the registry is too big.  Or perhaps the registry can be
> stored in a seperate Shm area or something...
True, but my registry would be too big to even fit in its own Shm segment
at all. So disabling Shm (for the registry only) if it's too big could
be a nice option. Maybe you could even use the Shm area for caching
registry values (ie when a program reads a value, the server places the
key (or even the key's parent) in the Shm. That way you will probably
still have the speed boost, but not the memory penalty. How's that?

Gr.

Matthijs