Tag Info

New answers tagged

1

Shared memory is a mechanism to exchange rendered image without having to use sockets, the protocol works something like this: X client create the shared buffer, X client tell the server that's where you will find the images i create, the server "attach" itself to the shared memory and refresh whenever there is an update, this mechanism is 10x of socket ...


0

Ok I think this points to a crash in the application, as I found that removing the following files got back the pages. Posting this in case it helps anyone else as a workaround for a buggy app! $ cd /dev/hugepages $ ls rtemap_0 rtemap_1 rtemap_2 rtemap_3 rtemap_4 rtemap_5 $ /bin/rm rte* $ cat /proc/meminfo | grep -i huge AnonHugePages: 133120 kB ...


0

/!!\ This is probably not a valid answer as this will take all of your traffic down with you, not just a single pid's traffic. I've not used it, but I think you could potentially use Comcast: https://github.com/tylertreat/Comcast set to 100% packet loss Again, I've not tested this, but theoretically, modified from their readme you can do: Linux ...



Top 50 recent answers are included