So I would interprete Your ideas as: an device link handling system
(used by all applications, which want to share the transforms) is
essential to set up and run such cache, without interfering from
application side - correct?
(I must say, I did not yet play with mmap-ing)
regards
Kai-Uwe Behrmann
+ imaging development / panoramas
+ color management
+ email: [EMAIL PROTECTED]
+ CMS proposal <www.behrmann.name>
Am 13.12.04, 11:41 -0600 schrieb Bob Friesenhahn:
> On Mon, 13 Dec 2004, Kai-Uwe Behrmann wrote:
>
> > The offsets can easily been exchanged through Oyranos, as well as the
> > othe parameters influencing the transform. As an option the chache can
> > been removed after switching the computer off.
>
> It is important to note that expecting a shared memory system to
> support the same memory offsets in all applications is not portable.
> Even if a system supports it, the ability is not supportable in all
> situations. For example, the desired address range might already be
> in use.
>
> This is why I recommended that if a transform is intended to be
> cacheable, the saved transform should not contain any raw pointers.
>
> Some systems support both 32-bit and 64-bit applications at the same
> time, so it is best that the transform footprint is concrete and not
> depend on any types which change their size based on the compilation
> model.
>
> Bob
> ======================================
> Bob Friesenhahn
> [EMAIL PROTECTED]
> http://www.simplesystems.org/users/bfriesen
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Lcms-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/lcms-user
