Giter VIP home page Giter VIP logo

cosmic-protocols's Introduction

COSMIC protocols (:construction: Work in Progress :construction:)

Continuous Integration LICENSE Docs

Additional wayland protocols and generated rust bindings used by the COSMIC desktop environment.

cosmic-protocols's People

Contributors

ids1024 avatar drakulix avatar wash2 avatar

Stargazers

Kennedy Tedesco avatar Lyu Ji avatar  avatar Ryan Brue avatar  avatar Povilas Brilius avatar theshank avatar Suraj avatar Erik Reider avatar Sophie Winter avatar Kerem Bozdas avatar HTGAzureX1212. avatar Erlang Parasu avatar Pedro Lara Campos avatar Eduardo Flores avatar  avatar Milad avatar Senn avatar

Watchers

Mike G. avatar  avatar Carl Richell avatar Michael Murphy avatar  avatar Ian Santopietro avatar  avatar Jeremy Soller avatar Suraj avatar Levi Portenier avatar  avatar  avatar

cosmic-protocols's Issues

export-dmabuf: provide driverUUID and deviceUUID

The export dmabuf protocol should provide the driver and device uuid along side the drm node of the device.

The driver and device uuids are defined in the following Vulkan/EGL extensions:

For vulkan in particular, knowing if the dmabuf is from the same driver and device can be used to optimize memory barriers (The driver uuid would differ if two different versions of Mesa are used across the Wayland socket).

If the driver and device uuids match, the implementation can perform queue family ownership transfer from the sentinel "external" queue family instead of having to use the sentinel "foreign" queue family. Testing by Nvidia's driver team showed that the more optimized memory barrier can lead to a 50% performance improvement in some cases.

Now this all sounds great, are there any protocol considerations that need to be made?

Well, using the external queue family on a dmabuf which is infact foreign leads to undefined behavior in Vulkan. This means the protocol MUST mandate that implementations provide the correct device and driver uuid.

The driver and device uuid fields must be optional. In that case clients must assume the worst and use the most conservative memory barriers.

If a compositor supports the driver and device uuid, the implementation must report both (probably by transmitting both in one event).

Anyways I hope that one day this protocol is standardized in Wayland protocols :)

Discussion: Work with wlroots to use their protocols rather than using a separate set

By design, Wayland has fragmentation in how protocols are handled, currently there being three main sets: KDE, GNOME, and wlroots.

I would suggest working with wlroots to use their protocols rather than using a separate set, so as to reduce fragmentation of the Linux desktop. This would also make it easier for utilities to support Cosmic, since they can just build for wlroots and it'll already work on Cosmic.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.