20 Nov 2026
planet.freedesktop.org
Matthias Klumpp: Changes on freedesktop.org!
Today we launched a change that has been a long time in the making: The updated website for freedesktop.org, as well as the refreshed wiki.freedesktop.org are live now!
You can read the announcement here, this blog post elaborates a bit on it and on the background of the changes, as well as future plans.
Why change anything?
The freedesktop.org website has been a wiki for a long time, which definitely was the right call in its inception. A wiki is very much in spirit of Freedesktop's mission statement to foster collaboration between desktop environments and to be a place to create de-facto standards.
However, over the years, working with the wiki became a bit of an issue: Not only did we face multiple spam-apocalypses (which in part motivated the switch to IkiWiki in 2013 and resulted in us heavily restricting write access to the wiki), but it also meant that official project information, finished specifications, half-finished proposals and pages nobody had touched in fifteen years were all sitting next to each other.
Since 2000 when Freedesktop.org was started, the project has grown so much and has had so many associated projects and specifications over the decades that it is now very difficult for new people to get an overview what is current and what state the software projects and specifications hosted by Freedesktop.org are in.
Having only a wiki as a large and somewhat disorganized pile of information did not help with that issue, so I worked to split things up: We now have a website as well as a wiki, using different designs to distinguish the two, and serving different purposes.
Website & website plans
The website at www.freedesktop.org will be the place for "official", or rather, more curated information. Now that the new website is live, its content is still largely that of the old wiki. Over the next weeks, I will be working on cleaning up its contents and listings. For example, I will clearly split active projects from archived ones, add missing ones, and also work towards synchronizing the specifications hosted on the former wiki / website with the ones listed on specifications.fd.o.
So, basically I will do an inventory check of Freedesktop. That work has already started, but until now, I could not make any public changes to not disrupt workflows or make my own future work harder by having diverging information in two places (website & wiki).
I also wanted to make it easier for people to find information on how to get involved with Freedesktop and associated projects, so the new website now has a more discoverable section for that.
The new website is a static site hosted via GitLab Pages and using Pelican. You can view its sources if you like.
Wiki changes
Of course, we also still want to keep the Wiki and all of its rich history around! It remains the easy-to-edit place for collaboration on upcoming projects and specifications.
Wiki edits must now happen through GitLab instead of the old IkiWiki web interface. While this sounds like an additional barrier to edit the wiki, it is significantly easier than requesting an account on annarchy to edit the old Wiki through the web interface. It also still allows us to keep the existing history as well as spam protection measures. In order to use the wiki with GitLab Pages and to keep the history easily accessible and readable, I rewrote the Git history of the wiki to make it pretend that all changes always happened in a content subdirectory. So, if commit signatures are missing and hashes are different: That is the only reason why. There have been no content changes or other metadata changes (and we still have a copy of the pristine wiki Git repository).
For the fd.o wiki, we are now also using Hari's IkiWiki template that is already in use on the X.org website and which is much easier on the eyes.
Next steps
At the moment, I am mostly concerned with ensuring that the change has not broken any existing links and all systems keep working. After that, the wiki 🡘 website deduplication work will start and we can modernize both the content of the website and wiki.
If you find a broken link, an outdated page or anything else that looks wrong, please file an issue or, even better, open a merge request.
For the wiki, you are very welcome to just fix or otherwise update the page directly.
I did reach out to all wiki editors and projects impacted by this change in advance, but since there are so many people and projects involved, it is always possible to miss someone or something. If you found a bug, need edit permissions, or need help with anything, don't hesitate to ping me: You can find me as ximion in OFTC's #freedesktop IRC channel, in the very recently created #xdg-specs channel on the Freedesktop Matrix space, or you can email me.
Thank you!
I do want to echo the announcement news post here: None of Freedesktop.org would exist without the people who filled it with life over the years and who worked on cross-desktop collaborative projects. I have read through a lot of wiki history and old project pages over the recent months, and it feels amazing to know how much work and passion people have poured into the projects and collaborative efforts over the years - no matter if they were successes in the end, or remained experiments. I am very thankful for all current, past and future editors of the website and wiki, as well as all project maintainers and contributors.
I also want to thank the Sovereign Tech Agency once more for supporting me in their fellowship program as a maintainer, which enabled me to work on this task among other things.
Thanks to all contributors, in whichever way you contribute to our free desktop ecosystem!
20 Nov 2026 10:22pm GMT
09 Nov 2026
planet.freedesktop.org
Ricardo Garcia: XDC 2026 CTS Talk
At the end of September I attended XDC 2026 in Toronto, where I gave a lightning talk about a memory usage problem we recently solved in Vulkan CTS. It was a lot of fun to meet again in person the people I work with every day, including many Igalia colleagues once more. I also enjoyed Toronto very much, and I had the chance to go up the CN Tower and enjoy the impressive views of the city from there.
You can find the recording of the talk below, followed by the slides and a transcription for those more inclined to read than to watch a video.
XDC 2026 Recording
Talk slides and transcription
Hello, I'm Ricardo from Igalia and I'm going to talk about a memory usage problem that we recently fixed in Vulkan CTS and what we learned while fixing it.
The situation was that the amount of memory needed by deqp-vk, the main Vulkan CTS binary, had been increasing along the years and it got to a point where it was starting to cause issues for CI systems.
I used Valgrind to measure the amount of memory that was used by the process and found out that the peak amount used, in my system, was around 900 MB. I analyzed the situation and, after doing some changes, I was able to decrease that number to around 300 MB on the same system.
How did we reach the initial situation and how did we solve it? That's what I wanted to explain today. It's actually very simple and we can apply the same change to more cases to improve the situation even more. In fact, I have a change under review that will bring the number down to 200 MB.
First, a bit of context.
CTS organizes tests in a tree. When we mention a test like dEQP-VK.api.smoke.triangle, the dots here separate the steps in the path from the root node, called "dEQP-VK", to the test case, called "triangle". Internally, "dEQP-VK", "api" and "smoke" are objects of a "test group" class, while "triangle", the leaf node in the tree that you can see colored green here, is an object of type "test case".
When a test case is run, it creates a sub-object called the "test instance" to run the actual test. Test instances are the ones allocating buffers, images, creating pipelines, etc, and doing most work, so it's natural to take a look at them first to see if some of them are problematic. However, it's more or less obvious, reading the CTS source code, that test instances have a very short lifespan. They destroy resources immediately and, because deqp-vk is single-threaded, we only have one instance alive at any given moment.
During the analysis, I immediately saw test instances were not the main issue, despite being the prime suspects, and Valgrind confirmed that most of the allocated memory was being used by test cases, not instances.
This was interesting because the lifetime of test cases and groups is not so clear at all when reading the source code. In fact, some pieces of code in CTS may lead you to believe most of the hierarchy of test cases and groups is created first and kept alive for a long time, but what I discovered while taking a close look is that that's not exactly true. What's true is that many pieces of code in CTS create large portions of the tree in a single step, including hundreds or thousands of test case objects that can be quite large. This is represented in the slide here. When the main subgroup is created, the whole subtree is immediately created with it. If the test cases are large, the program uses a lot of memory.
When I saw a lot of allocations belonged to test cases, my first reaction was analyzing why those test cases were so large and how to make them smaller, but it turned out I was missing the forest for the trees. Taking a couple of steps back, I noticed CTS has an internal mechanism that allows us to avoid creating child nodes in the tree until the moment we enter the parent node to do something with it, and the same mechanism deletes those child nodes once we're done. In other words, this mechanism allows us to keep in memory only the portion of the tree that we're really working with at a given moment. The main problem is that this mechanism is not always used and, because this is not obvious, not documented in the source, not used in many many cases and it normally does not create a huge problem, some CTS developers, including myself, may not even know it exists or, if they know, they may not realize how it really works and plays a major role in the amount of memory used by the process.
When we use that mechanism properly and we divide cases in small groups, we're able to have only a few test cases alive at the same time in memory, and we could reduce peak memory needs by a large amount, even if the test cases are large. Converting some groups to this mechanism is what allowed us to go from 900MBs to 300MBs. Of course, in the long term we need to analyze why those test cases are so large and how they can be redesigned to be smaller, but that can be difficult. In contrast, changing the way test cases are created to take advantage of this is usually not hard and the mechanism is a very powerful tool to attack the memory usage problem. The main conclusion is that there's no excuse for deqp-vk to need a lot of memory, except maybe to run a particular test for a very short amount of time.
If you have issues related to this, please reach out. Thank you!
Hallway comments
Since it was a lightning talk, there was no Q&A section, but I got a few comments in the hallway after the talk. The summary is that the changes we made to use delayed creation for some of the affected tests also make tree traversal faster when you only select some tests, or even a single one. The reason is that deqp-vk is smart enough to check, before expanding a group, if the partial test name so far matches any of the given globs, and it does not expand the group if it doesn't. With delayed creation, the subtrees of groups that are not expanded are never created, so we avoid paying the cost of creating the whole hierarchy and the selected tests start running earlier.
09 Nov 2026 5:21pm GMT
30 Oct 2026
planet.freedesktop.org
Mike Blumenkrantz: Friday NV Fight
A Final Frontier
I've looked at perf in a lot of places. I looked between the seats, under the couch, in the jar where I usually leave it, but until recently I'd never looked in one place. It was too scary. Too complex.
Seriously, how do you even build mesa on Windows?
I don't know, and I don't feel my life will be enriched by finding out. But I was still curious about one thing: How does zink stack up against the industry-standard, the titan of GL, the Windows NVIDIA proprietary driver?
In The Green Corner
The reigning heavyweight champ, the driver preferred by gamers and industry afficianados alike! They wrote (many of) the specs, they implemented (many of) the extensions, their driver has no bugs at all (because apps have collectively turned these bugs into a standard-but-wrong dialect of OpenGL)!
NVIDIA, v617.14!
In The Open Corner
The only open source graphics stack out there using a quarterly versioning scheme! Despite shipping a new major release only a month ago, that release is already obsolete! These drivers are hungry for perf, and they'll stop at nothing to get it!
Mesa, <my own wip set of patches which are mostly upstream but not all upstream and so I do not have a specific commit hash>!
Epic Matchup
I won't tell you which one I am in the picture, but my office does have a helmets-required policy. Setup went fine (computer, set up the Windows build!) while I did real work, and then it was off to the races.
The first results were… Well, they weren't as bad as expected. But there were some inconsistencies, which is to say that zink wasn't winning hard enough. Or at all in a couple cases. It came down to the wire with the weekend looming, but ultimately I was able to learn the underhanded tricks that NVIDIA GL was using to stay ahead.
Questionably Ethical Optimizations
There are (apparently?) some real weaknesses in NVIDIA hardware, specifically with line drawing. To get around this, they cut some corners.
First up: smooth lines on color attachments with float formats. Apparently this is 50x slower (literally) than using rectangular lines. So they just draw rectangular lines. I know what you're thinking-You're thinking Mike, that's gotta be a spec violation. And yes, it is. And I know what you're thinking next-You're thinking Mike, how can they possibly pass CTS like that? And the answer is easily, because there are (very conveniently) zero tests anywhere in the ecosystem for this combination. Not in CTS, not in piglit, not even under the couch.
DJ Khaled (anotha one): list topology draws with primitive restart enabled are about 5x slower because processing the restart indices is somehow very, very slow. NVIDIA gets around this by preprocessing index buffers in compute shaders any time this combination occurs. Nothing illegal about it since the solution is conformant, it's just a little weird that they have to.
Monkey See, Monkey Do
Yeah, I did the same things. Even on a pure Mesa stack, NVK is still 3-9x slower for list topology restarts and 5x slower for the float-format lines, so this is likely something at the hardware level that won't be fixed by a VK driver. The float-format change was trivial, but the index buffer rewrite ended up being more complex. I got about halfway through trying to convert util_prim_restart_convert_to_direct to a compute shader before I started wondering whether this was the optimal choice.
Turns out it wasn't. A more optimal choice is a three-pass shader using subgroups which consume chunks of the input index buffer:
- count the primitives that will actually be drawn and set
flagif there are any which contain both real and restart indices - prefix-sum the counts from the previous pass into the offsets used by the next pass, then write the eventual draw command (total primitives drawn, or the original draw if previous pass set
flag) - write the indices using the offsets from the second pass (or copy all indices without change if the
flagis set)
Then use the resulting buffer for an indirect draw.
Power Overwhelming
SPECviewperf 2020
| viewset | tests | native (best) | zink | zink / native |
|---|---|---|---|---|
| catia | 8 | 124.83 | 228.94 | 1.83 |
| creo | 13 | 121.04 | 191.64 | 1.58 |
| energy | 6 | 91.93 | 111.71 | 1.22 |
| maya | 2 | 693.69 | 738.16 | 1.06 |
| medical | 10 | 65.39 | 77.50 | 1.19 |
| snx | 10 | 40.13 | 865.09 | 21.56 |
| sw | 10 | 457.11 | 548.98 | 1.20 |
Geomean: 2.194 over 59 tests.
SPECviewperf 15
| viewset | tests | native (best) | zink | zink / native |
|---|---|---|---|---|
| blender-01 | 7 | 99.64 | 126.31 | 1.27 |
| catia-07 | 5 | 80.68 | 106.16 | 1.32 |
| creo-04 | 13 | 118.60 | 199.99 | 1.69 |
| energy-04 | 6 | 91.64 | 110.16 | 1.20 |
| maya-07 | 7 | 234.01 | 251.66 | 1.08 |
| medical-04 | 10 | 64.78 | 78.71 | 1.22 |
| snx-05 | 8 | 45.29 | 68.90 | 1.52 |
| solidworks-08 | 8 | 55.28 | 67.52 | 1.22 |
Geomean: 1.332 over 64 tests.
Superposition
| preset | native | zink | zink / native |
|---|---|---|---|
| Medium | 28928 | 34668 | 1.20 |
| Extreme | 14837 | 14770 | 1.00 |
The results are pretty one-sided. I won't claim that they hold for every possible case, but viewperf and superposition combined give a reasonable picture of OpenGL performance. If you want the best GL experience on your green hardware and don't need NV-specific extensions, you should try using zink.
…With Some Caveats
The cases here were run three ways:
- NVIDIA (threaded optimizations disabled)
- NVIDIA (threaded optimizations enabled)
- zink (
ZINK_DESCRIPTORS=lazy)
I used the best of the NVIDIA results (though they didn't vary hugely between the modes), but I didn't use ZINK_DESCRIPTORS=db because I was pressed for time and this is known (supposedly) to be slightly slower on NVIDIA hardware. Probably not more than 5% from my testing, so it only affects the margins. I'll probably just build out ARB_separate_shader_object handling for 1.0 descriptors (currently only supported for db because I was lazy) and then switch NVIDIA over to it by default. I imagine I could bang that out in an afternoon and a hundred lines of code. No, I still don't plan to add descriptor heap support; I don't need to maintain another 2k+ lines of descriptor code when the current solution works fine.
There are also some patches which probably won't get upstreamed until next year. In particular, the ray-marching loops in viewperf's energy viewsets perform extremely poorly due to loop optimization deficiencies in NVIDIA's compiler stack. I have some hacky stuff to work around this, but I'd rather wait for some upcoming NIR work that's being done by people more compiler-y. It only seems to affect these very specific shaders anyway, so unless you're doing that type of work you won't notice. But if you are, it's about 40% worse until Mesa lands more loop optimizations. NVK is unaffected.
Anyway, mesa's pretty fast. Oh yeah, and here's WGL glthread support.
30 Oct 2026 12:00am GMT





