[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
short introduction to shared memory support ?
From: Alexander Neundorf ####@####.#### Date: 14 Dec 2005 22:04:48 +0000 Message-Id: <200512142304.23604.neundorf@kde.org> Hi, how is the shared memory support in microwindows designed ? A socket is still used, e.g. for the flush. I guess a shared memory segment is created when a client connect to the server ? Are the complete requests put in the shared memory region or only the parameters ? Thanks for any pointers Alex -- Work: ####@####.#### - http://www.jenoptik-los.de Home: ####@####.#### - http://www.kde.org ####@####.#### - http://www.neundorf.net | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] short introduction to shared memory support ?
From: "Greg Haerr" ####@####.#### Date: 15 Dec 2005 01:45:18 +0000 Message-Id: <0b9501c60118$ee10d040$6401a8c0@winXP> : how is the shared memory support in microwindows designed ? : A socket is still used, e.g. for the flush. Shared memory support was contributed some time ago as an add-on, for cutting down large buffer copies for image display. Few routines actually take advantage of a shared segment. : I guess a shared memory segment is created when a client connect to the : server ? Yes, since if compiled in, they must work, given the current code. : Are the complete requests put in the shared memory region or only the : parameters ? Usually only the image data, and not the entire request nor parameters. This could possibly be enhanced or redesigned. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |