<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, Fabio! Sorry for long silence. <pre class="moz-signature" cols="72">Kind regards Yury Shvedov</pre> <div class="moz-cite-prefix">On 03/07/2016 12:12 AM, Fabio Fantoni wrote: </div> <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> Il 06/03/2016 13:25, Yury Shvedov ha scritto: <blockquote cite="mid:56DC21CE.1070500@lvk.cs.msu.su" type="cite"> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> Hi, Fabio! I made 3 new commits. First one updates code to work with new Spice API. Here, as I think, must be Spice version check if for example in Debian 8 it less than 0.11. </blockquote> Debian 8 have spice-server 0.12.5, debian 7 with backports have 0.12.4, in any case is good added a check in configure for minimum required version, I did a commit with >=0.11.2 check based on your api update, from a fast look I didn't saw newer api. Other optional cases (like lz4) is/will be with define. Spice compositor differently from rdp one now should support some stable versions. This I think is good to avoid rdp compositor problem that make it after some years still unable in some major distros: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775855">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775855</a> (was blocked by 814676 - update freerdp) There are other cases that make the maintainer of solid distributions refractory to support it. </blockquote> OK then! =) <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> <blockquote cite="mid:56DC21CE.1070500@lvk.cs.msu.su" type="cite"> Second one is regarding your remarks. I hurried too much with editing your commits. I'm sorry. So I left your logic but in another stile. I used "int compression" to handle invalid data. But than found SPICE_IMAGE_COMPRESS_INVALID value and changed the variable type back to spice_image_compression_t. I think this part is OK now, but if you have something to say or change there, fill free to do it =) </blockquote> Thanks, seems very good, in wan compression options case is also better having specific error message on each option. I did some commits: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/Fantu/compositor-spice/commits/test3">https://github.com/Fantu/compositor-spice/commits/test3</a> Can you cherry-pick since after "Add Spice compositor" if are ok for you. </blockquote> Done! Almost without changes. =) <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> About the wan compression patch I did it very fast and I only checked build (success) but I not tested it and is possible that have error or unexpected cases doing it fast, I'll try to do other tests now if I have enough time but I'm not sure. </blockquote> I'll try too when I'll find much time. <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> <blockquote cite="mid:56DC21CE.1070500@lvk.cs.msu.su" type="cite"> Third - I remove some rubbish like dprint from my old code. But I'm afraid, there still much to do in this sphere. Will be perfect if you make the revue, but not now - we have more important things to do. For example, next I'm going to read the code of compositor-rdp much closely to understand how it works. This needed to know did we miss something. The second thing after that - is to render the screen on the client side. Now whole images composed on the server and sent fully to the client. </blockquote> If will be possible do rendering and image "difference" with opengl (or probably better also with vulkan) I think can be very useful. </blockquote> This was the main idea of my diploma. More over, my old university fellow managed to make the drm device work with non-framebuffer memory. We planned to merge our work at the end, but the fate decreed otherwise. The problem, I'm thinking to solve here, is that the frameworks (GTK+ or Qt) uses their own drawers like Cairo to update the windows and sends to desktop manager the whole new window. <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> Spice developers added recently spice-egl for support rendering of vm using virgl with 3d but now is only local. </blockquote> I don't know what they do, but I thought about the next: <ol> <li>calculate the more accurate region of damage </li> <li>recognize the type of damage:</li> <ul> <li>full image replacement (buttons, radios, etc): we can cache the control elements on client side to reuse them instead of resending </li> <li>text: spice can send the text maybe we can use this somehow. </li> <li>scrolling: in this case instead of sending whole damage, we can send just the little strip of the region edge. </li> <li>complex changes (movie, game, add): nothing to do here, compress and send as is. </li> <li>the combination: the add in browser while scrolling. </li> </ul> <li>handle each type of damage by its own way. </li> </ol> This will decrease the amount of data to render remotely (except the 3rd case). I'm afraid that this is kind of utopia too, but in theory it is possible with using the shaders. <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> For remote I don't know if there is something in progress. I thinked about better possibility to solve improve latency/efficiency doing all directly with opengl or vulkan (with vk should be possible better manage resources) do directly texture compressed (to avoid some software steps in that I fear most are the leading cause of latency and inefficiency), I saw bc7 that seems to have high quality, alpha support and is mandatory in vulkan but probably still requires too much bandwidth. Alternative with streaming with lossy codec like gstreamer project in development (I already tested in vm) seems too many greedy of resources and with too many latency. So I do not know if my idea can be implemented in practice or is just utopia. I have too little knowledge to better evaluate. </blockquote> This is another way of using GPGPU in our case. May be we need to look here first. <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> I suppose start look rdp and trying to improve generic solution compatible also without hardware acceleration (to keep it usable for all users/cases) is a good/fast thing to do initially as what seems you want already do, after we'll think about utopian things. </blockquote> Just exactly what I was going to say! =) <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> Another thing to look interesting is screen sharing plugin now usable only with rdp, if will be possible add spice support easy/fast probably will be good but I not looked its code for now. (I suppose can be very useful for user remote assistance thing like teamviewer, I suppose that this with spice full features will be better that teamviewer and similar) </blockquote> Yes, I noted this too. <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> <blockquote cite="mid:56DC21CE.1070500@lvk.cs.msu.su" type="cite"> By the way! Thank you again for your help! =) P.S. What did you learn about vdagent?</blockquote> Is very useful (required for mouse client mode, clipboard copy, file transfert, ecc...) I saw the difference for example in xen when now pv domUs can't support it and is remarkable. It is already implemented in xspice but with a fast look seems have xorg specific things. I didn't investigated in detail for now. </blockquote> OK will remember this and return to <blockquote cite="mid:56DC9D3F.1090006@m2r.biz" type="cite"> Sorry for my bad english. </blockquote> But now I suggest you and me to return from sky back to earth. We have many things to do. HW acceleration, vdagend, screen sharing, compression and authentication is good points. But without any acceptable performance they are useless. Firstly we need to be not worse than rdp-compositor and we know how to achieve this. In my opinion it is better for us to stop surfing such interesting things like vdagent and vulkan and concentrate on more important things. Honestly, I spent an our, writing this reply (5 minutes I spent on your commits). I think you spent much time too looking for technology. In fact this was important and realy useful. But now I suggest us to spend this time for nearest problems. What do you think? =) </body> </html>