nanogui: Thread: About speeding up drawing image in the nanox

Hi, 

I have read the email with topic "API with point as parameter!". Something has interested me. I am working on speed up drawing image in the nanox.
When you draw an image or bitmap and so on, you will send a pointer which indicate the head address of image array in the client address, however I guess that this array which store all points information of an image should be sent to the server over the socket as though its formal parameter is a pointer, because only graphic server can perform drawing the image. This is just a guess. If so, the time used in translating these information may be very long, whether I can speed up drawing an image through just passing the pointer to the server.  Because I have ported the microwindows to the m68kez328 target platform which has no mmu, all process share the physical memory. I can’t make sure this idea is feasible. Would you like to give some advices on this? Any help will welcome. Thank you in 

advance.





Wang weihui

: When you draw an image or bitmap and so on, you will send a pointer which
indicate the head address of image array in the client address, however I guess
that this array which store all points information of an image should be sent to
the server over the socket as though its formal parameter is a pointer, because
only graphic server can perform drawing the image. This is just a guess. If so,
the time used in translating these information may be very long, whether I can
speed up drawing an image through just passing the pointer to the server.
Because I have ported the microwindows to the m68kez328 target platform which
has no mmu, all process share the physical memory. I can’t make sure this idea
is feasible. Would you like to give some advices on this? Any help will welcome.
Thank you in


Yes, this could work, and is already somewhat used
when you turn on the shared mem (HAVE_SHAREDMEM_SUPPORT=Y)
in the config file.  When on, only pointers are passed
between client and server, and the shared memory
is used for the data.  If you used this method, then
no API changes would need to take place, and it should
all work.  See nanox/client.c and nanox/nxproto.c
for the shared memory stuff.

Regards,

Greg