{"id":1258,"date":"2008-01-19T02:54:46","date_gmt":"2008-01-19T00:54:46","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2008\/01\/kde-and-the-linux-kernel\/"},"modified":"2008-01-19T02:54:46","modified_gmt":"2008-01-19T00:54:46","slug":"kde-and-the-linux-kernel","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2008\/01\/kde-and-the-linux-kernel\/","title":{"rendered":"KDE and the Linux Kernel."},"content":{"rendered":"<p>Just returned from a break-out session with some kernel developers who are here at Google where we<br \/>\n    discussed a couple of things that can be improved in the current Linux kernel for a better<br \/>\n    user experience. We, that is a group of KDE people from different areas, among which aseigo, Dirk,<br \/>\n    Thiago, Will, Zack &#8212; in randomly alphabetical order. Kernel people in this session include Natalie<br \/>\n    Protasevich, Andrew Morton, Daniel Phillips and Gary Greene.<\/p>\n<p \/>\n    Issues that have been discussed are limitations in inotify where we&#8217;d like to be able to watch more<br \/>\n    files at once for changes, the most notable use case being desktop search and indexing. Another<br \/>\n    interesting issue we&#8217;re facing is bad guessing when trying to keep interesting things (such as a<br \/>\n    maildir with lots and lots of small files in cache) when dealing with large I\/O. This is actually<br \/>\n    something we can improve ourselves by using fadvise to tell the kernel what makes sense &#8212; the kernel<br \/>\n    cannot reasonably be expected to know the purpose and usage of data, so we need to tell it somehow.<\/p>\n<p \/>\n    Of course, my pet-peeve and the ever-interesting issue of suspend is another big issue with the Linux<br \/>\n    kernel we currently have. While it is on the radar of the kernel devs, we made sure that they<br \/>\n    know how important that is to us. In my opinion, the solution to this is two-fold. As it&#8217;s mostly<br \/>\n    drivers that are responsible for the rather bad user experience currently, drivers need to be improved.<br \/>\n    Open drivers can obviously be fixed much easier for the kernel developers, but it also helps if<br \/>\n    large companies can kick each other when they&#8217;re screwing up suspend and hibernate.<\/p>\n<p \/>\n    Most important outcome of this meeting has probably been the opening of communication channels.<br \/>\n    Andrew told us that the best way to get our issues addressed is filing bugs (as emails), voting<br \/>\n    for them to justify resources put into them. Andrew also told us that sending such a bugreport<br \/>\n    from a @kde.org email address will prioritise it, which is I think important to know for us. Kernel<br \/>\n    people really want to help us, getting them the information they need will make it easier to fix<br \/>\n    problems we face when using the Linux kernel. Such a bugreport ideally includes a testcase (code!)<br \/>\n    which shows the problem.<\/p>\n<p \/>\n    Needless to say that I&#8217;m very happy we got the chance to exchange. Thanks everybody involved! Also,<br \/>\n    I should probably pass on Daniel&#8217;s &#8220;Thank you for creating KDE!&#8221; to you all.<\/p>\n<p \/>\n","protected":false},"excerpt":{"rendered":"<p>Just returned from a break-out session with some kernel developers who are here at Google where we discussed a couple of things that can be improved in the current Linux kernel for a better user experience. We, that is a group of KDE people from different areas, among which aseigo, Dirk, Thiago, Will, Zack &#8212;&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2008\/01\/kde-and-the-linux-kernel\/\">Continue reading <span class=\"screen-reader-text\">KDE and the Linux Kernel.<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1258","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1258","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1258"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1258\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}