Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754191AbbDOOHp (ORCPT ); Wed, 15 Apr 2015 10:07:45 -0400 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:43244 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752289AbbDOOHh (ORCPT ); Wed, 15 Apr 2015 10:07:37 -0400 Date: Wed, 15 Apr 2015 15:06:58 +0100 From: One Thousand Gnomes To: Greg Kroah-Hartman Cc: Jiri Kosina , Al Viro , Borislav Petkov , Andy Lutomirski , Linus Torvalds , Andrew Morton , Arnd Bergmann , "Eric W. Biederman" , Tom Gundersen , "linux-kernel@vger.kernel.org" , Daniel Mack , David Herrmann , Djalal Harouni Subject: Re: [GIT PULL] kdbus for 4.1-rc1 Message-ID: <20150415150658.0b33410c@lxorguk.ukuu.org.uk> In-Reply-To: <20150415124134.GC20554@kroah.com> References: <20150414192357.GA6107@kroah.com> <20150414192429.GC26075@pd.tnic> <20150414193229.GB6107@kroah.com> <20150414194004.GG889@ZenIV.linux.org.uk> <20150414194804.GB7540@kroah.com> <20150415113727.0cfd5224@lxorguk.ukuu.org.uk> <20150415114936.GD19274@kroah.com> <20150415130354.458abfc2@lxorguk.ukuu.org.uk> <20150415124134.GC20554@kroah.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1913 Lines: 48 > operating systems anymore. Those "legacy" oses provide a system bus > that allows them to send thousands of queries just fine, but when moving > to Linux, we don't have anything other than D-Bus, so their library is > ported to use it, and they have to handle their old applications that > need/want the zillions of messages. And if you look at those systems btw many of them have a very compact, very clean very simple message passing interface,often in the hundreds not tens of thousands of lines of code. > People take those stateless models and build stateful ones on top of > them, yes, it's great. But you still need a stateful model somewhere in > order to be able to achieve many things (think a shopping cart > application). We put the IP stack in the kernel not the shopping cart. A good shopping cart of course only has state on the client. > Anyway, this is getting off-topic, there is very little "state" in the > kdbus kernel code here, other than a naming database that Havoc and > Simon explain the need for, and the normal lifecycle of kdbus "nodes" > (new, linked, active, inactive, drained, freed). I'm not convinced the naming data belongs in kernel beyond the simplest of "node 147". I'd offer a sort of proof by armwaving of this that if you have /dev/dbus/014 /dev/dbus/027 etc you can add a symlink to /dev/dbus/014 of /dev/dbus-by-name/gnome-wombat-grooming-daemon or whatever and we do that today for every other naming database and static allocation we've spent the past 15 years evicting from the kernel. That state isn't then held in a daemon that can crash nor is it invisible to debuggers, user tools and admins. Alan -- 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/