aboutsummaryrefslogtreecommitdiff
path: root/shm.h (follow)
Commit message (Collapse)AuthorAgeLines
* render: re-write cell clipping to use pixman destination clippingDaniel Eklöf2020-06-04-2/+3
| | | | | | | | | | | | Our home rolled clip-to-cell code was, obviously, not correct. The original problem was that we couldn't use pixman clipping since we have multiple threads writing to the same pixman image, and thus there would be races between the threads setting clipping. The fix is actually simple - just instantiate one pixman image (referencing the same backing image data) for each rendering thread.
* shm: make max pool size user configurable (via a 'tweak' setting)Daniel Eklöf2020-03-25-0/+1
|
* shm: scroll: keep shm pool around, and fix its size at max allowedDaniel Eklöf2020-03-25-3/+7
| | | | | | | | | | | | | | | | | This lessens the burden on (primarily) the compositor, since we no longer tear down and re-create the SHM pool when scrolling. The SHM pool is setup once, and its size is fixed at the maximum allowed (512MB for now, 2GB would be possible). This also allows us to mmap() the memfd once. The exposed raw pointer is simply an offset from the memfd mmapping. Note that this means e.g. rouge rendering code will be able to write outside the buffer. Finally, only do this if the caller explicitly wants to enable scrolling. The memfd of other buffers are sized to the requested size.
* shm: scroll: implement offset wrap-aroundDaniel Eklöf2020-03-24-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Impose a maximum memfd size limit. In theory, this can be 2GB (wl_shm_create_pool() is the limiting factor - its size argument is an int32_t). For now, use 256MB. This is mainly to reduce the amount of virtual address space used by the compositor, which keeps at least one mmapping (of the entire memfd) around. One mmapping *per terminal window* that is. Given that we have 128TB with 48-bit virtual addresses, we could probably bump this to 2GB without any issues. However, 256MB should be enough. TODO: check how much we typically move the offset when scrolling in a fullscreen window on a 4K monitor. 256MB may turn out to be too small. On 32-bit shm_scroll() is completely disabled. There simply isn't enough address space. * Wrapping is done by moving the offset to "the other end" of the memfd, and copying the buffer contents to the new, wrapped offset. The "normal" scrolling code then does the actual scrolling. This means we'll re-instantiate all objects twice when wrapping.
* shm: scroll: move top/bottom region handling from renderer into shmDaniel Eklöf2020-03-23-1/+3
| | | | | This allows us to restore the regions without copying the contents to temporary memory.
* shm: add shm_can_scroll()Daniel Eklöf2020-03-23-0/+1
|
* shm: new function, shm_scroll()Daniel Eklöf2020-03-22-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This function "scrolls" the buffer by the specified number of (pixel) rows. The idea is move the image offset by re-sizing the underlying memfd object. I.e. to scroll forward, increase the size of the memfd file, and move the pixman image offset forward (and the Wayland SHM buffer as well). Only increasing the file size would, obviously, cause the memfd file to grow indefinitely. To deal with this, we "punch" a whole from the beginning of the file to the new offset. This frees the associated memory. Thus, while we have a memfd file whose size is (as seen by e.g. fstat()) is ever growing, the actual file size is always the original buffer size. Some notes: * FALLOC_FL_PUNCH_HOLE can be quite slow when the number of used pages to drop is large. * all normal fallocate() usages have been replaced with ftruncate(), as this is *much* faster. fallocate() guarantees subsequent writes wont fail. I.e. it actually reserves (disk) space. While it doesn't allocate on-disk blocks for on-disk files, it *does* zero-initialize the in-memory blocks. And this is slow. ftruncate() doesn't do this. TODO: implement reverse scrolling (i.e. a negative row count).
* shm: new functions: shm_cookie_*()Daniel Eklöf2020-03-18-0/+5
| | | | These functions return a SHM cookie given a terminal instance.
* shm: automatic buffer purging is now delayed one cycleDaniel Eklöf2019-11-02-0/+2
| | | | | This ensures we don't purge a buffer that a user is holding a reference to.
* shm: add shm_purge()Daniel Eklöf2019-11-01-0/+2
| | | | Destroys *all* buffers associated with the specified cookie.
* shm: associate a 'cookie' with each bufferDaniel Eklöf2019-11-01-1/+4
| | | | | | | When re-using a buffer from cache, only re-use ones with a matching cookie. This prevents contention between multiple terminal windows.
* shm: get_buffer(): remove 'copies' argument; it's not usedDaniel Eklöf2019-11-01-2/+1
|
* shm/render: there's no need to have one pixman image per threadDaniel Eklöf2019-08-16-3/+1
|
* Remove all references to cairo; we now use pixman onlyDaniel Eklöf2019-08-16-5/+2
|
* wip: render background and glyphs using pixmanDaniel Eklöf2019-08-16-0/+4
|
* wip: initial multithreaded rendererDaniel Eklöf2019-07-29-3/+4
|
* initial commit: maps an XDG toplevel windowDaniel Eklöf2019-06-12-0/+24