Explore >> Select a destination
|
You are here 
|
lists.swift.org | ||
| | | | |
www.miskatonic.org
|
|
| | | | | ||
| | | | |
lists.mindrot.org
|
|
| | | | | ||
| | | | |
nathanchance.dev
|
|
| | | | | Occasionally, I will forget to link something from the mailing list in this post. To see my full mailing list activity (patches, reviews, and reports), you can view it on lore.kernel.org. Linux kernel patches Build errors: These are patches to fix various build errors that I found through testing different configurations with LLVM or were exposed by our continuous integration setup. The kernel needs to build in order to be run :) | |
| | | | |
aivarsk.com
|
|
| | | I have built several scripts for monitoring Oracle Tuxedo over the years. Most relied on the tmtrace and tputrace(3c) features provided by Tuxedo itself. I also tried to collect statistics on the IPC queues using standard system calls and tools. But all these years I have been thinking about how to measure the time a message spends in a queue. Messages in IPC queues are just an array of bytes, there is no field I could use to store that information. IPC queues were not created with observability in mind. | ||
