Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933712AbbFWXT4 (ORCPT ); Tue, 23 Jun 2015 19:19:56 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:33611 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752275AbbFWXTt (ORCPT ); Tue, 23 Jun 2015 19:19:49 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 23 Jun 2015 16:19:49 -0700 X-Google-Sender-Auth: 5U5jceiJSrjCLFmIApbZWcxLOeA Message-ID: Subject: Re: kdbus: to merge or not to merge? From: Linus Torvalds To: Andy Lutomirski Cc: "linux-kernel@vger.kernel.org" , David Herrmann , Djalal Harouni , Greg KH , Havoc Pennington , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Daniel Mack Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1827 Lines: 38 On Mon, Jun 22, 2015 at 11:06 PM, Andy Lutomirski wrote: > > Can you opine as to whether you think that kdbus should be merged? I > don't mean whether you'd accept a pull request that Greg may or may > not send during this merge window -- I mean whether you think that > kdbus should be merged if it had appropriate review and people were > okay with the implementation. So I am still expecting to merge it, mainly for a rather simple reason: I trust my submaintainers, and Greg in particular. So when a major submaintainer wants to merge something, that pulls a *lot* of weight with me. That said, I have to admit to being particularly disappointed with the performance argument for merging it. Having looked at the dbus performance, and come to the conclusion that the reason dbus performs abysmally badly is just pure shit user space code, I am not AT ALL impressed by the performance argument. We don't merge kernel code just because user space was written by a retarded monkey on crack. Kernel code has higher standards, and yes, that also means that it tends to perform better, but no, "user space code is shit" is not a valid reason for pushing things into the kernel. So quite frankly, the "better performance" argument is bogus in my opinion. That still leaves other arguments, but it does weaken the case for kdbus quite a bit. Because go out and read pretty much any argument for kdbus, and the *first* argument is always performance. The articles never say ".. because the user-space dbus code is crap", though. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/