ethtool ops for netdevsima project by mkubecek This can be seen as a subproject of ethtool netlink interface but from the technical view it's independent. Every new piece of software is going to be buggy and with frequent changes and rewrites, new regressions are introduced. Automated selftests can help a lot but as ethtool deals with hardware devices, we do not want these tests to depend on a specific hardware. The netdevsim driver was created as a virtual device which (unlike e.g. dummy) cannot be used for actual network traffic but implements various configuration interfaces so that it can be used for their (automated) testing. 
|
|
dmidecode: no more open-coded printfsa project by jdelvare There's a long standing request to extend the output of dmidecode to something that would be machine-readable. Something like an XML or JSON-based format. Unfortunately this can't be implemented right now because the output of dmidecode is generated by open-coded printfs as the DMI table is being parsed, with no intermediate structures nor temporary buffers. While implementing a machine-parseable output is out of scope for a single hack week, let's remember that even the longest journey starts with a single footstep. I would like to try and rewrite the 5200 lines of code of dmidecode in such a way that printing the output would be somewhat separated from parsing the DMI table and done by a limited set of dedicated functions. Alternative output formats could later hook into such functions. 
|
make "predictable network interface names" more predictablean idea by mkubecek Since the so-called "predictable names" for network interfaces were introduced, the concept and mainly its implementation has been a target of a lot of critique and sometimes even hate. On the other hand, similar idea works reasonably well for block devices. In my opinion, the main reason why "predictable names" reception was not nearly as good as for block devices is the difference in how the implementation works. For block devices, the device name provided by kernel is preserved and other names based on multiple naming schemes (by path, by UUID, by various device identifiers) are created as symlinks so that all of them (including the original kernel one) can be used simultaneously. On the other hand, network interface has only one name and as it is not represented by a file, symlinks cannot be used for aliases. Therefore even if there are multiple naming schemes (e.g. based on BIOS enumeration, bus address etc.), only one of them can be used for each network device and it's rather unpredictable which one is it going to be. Moreover, some of the generated names are rather long, ugly and inconveninent and unlike with block devices, one cannot just ignore them and use a different name (e.g. one provided by kernel). |
Phoebe - where AI meets Linuxa project by mvarlese Project DescriptionPhoeβe (/ˈfiːbi/) wants to add basic artificial intelligence capabilities to the Linux OS. 
|
multipath-tools: cleaner model for path device informationan idea by mwilck Project DescriptionObtaining correct information about devices in the system is crucial for multipath-tools. Properties of devices depend on each other. Certain properties matter in some parts of the code and some in others. |
multipathd: improve asynchronous behavioran idea by mwilck Project Descriptionmultipathd is multi-threaded, but it uses a single lock that essentially kills most benefits of |
multipath-tools: improve CIa project by mwilck Project Descriptionmultipath-tools is in urgent need of better CI, both unit tests and "real world" tests. We a very basic set of unit tests, but the coverage is miserable. Also, there's some minimal github workflow code, which could be improved a lot while I'm learning about github workflows. 
|
multithreaded network benchmarkan invention by mkubecek Project DescriptionThere are multiple network benchmark tools already, most popular probably being netperf and iperf. Each of them has its pros and cons but the biggest drawback probably is that netperf runs only one connection (flow) and while iperf can use multiple connections, it still runs in a single thread. For benchmarking of contemporary fast networks like 40Gb/s or 100Gb/s ethernet, this can be a severe limitation as the performance is often CPU bound. Even on 10Gb/s ethernet, we are often unable to saturate the medium if tunneling or complex packet processing is involved.
|
NeoMutt: Show index and body of emails in a horizontal splitan invention by iivanov Project DescriptionI'd like to have NeoMutt show an index of emails at the same time as the body of the selected email, horizontally next to each other. 
|
|
Add GObject based introspectable API to libzyppa project by zbenjamin Project DescriptionCurrently we are in a situation with libzypp where we have a C++ based and hard to use API. Due 
|
Improving picotm
Use ESP-01S as WiFi to UART bridge