Tile manager and Mutex and desinging for threading

[Boudewijn Rempt]

On Monday 04 June 2007, Cyrille Berger wrote:

> I don't think one lock on the datamanager lock the entire paint device, as
> you only need to "speak" with it when fetching a tile. So right, one lock
> on the tilemanager, serialize access to the swapfile, while one lock to the
> datamanager serialize getting new tiles.

Isn't the memory for new tiles also coming from the tilemanager?

> > And, yes, a dedicated thread for memory management would be cool. It
> > would also be the place to do the compression of (undo) tiles before
> > swapping them out.
>
> yup. I hope Bart is taking notes of cool stuff to do :D

I've just committed a small cleanup -- remove the two separate locks for pool 
and swap -- because all of the tilemanager was already locked by the BKL so 
the extra two locks were superfluous.

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kimageshop/attachments/20070604/f7fa4b31/attachment.pgp