Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754372AbbDONWv (ORCPT ); Wed, 15 Apr 2015 09:22:51 -0400 Received: from mail.skyhub.de ([78.46.96.112]:35154 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751618AbbDONWm (ORCPT ); Wed, 15 Apr 2015 09:22:42 -0400 Date: Wed, 15 Apr 2015 15:20:19 +0200 From: Borislav Petkov To: One Thousand Gnomes Cc: Greg Kroah-Hartman , Richard Weinberger , Andy Lutomirski , Al Viro , "Eric W. Biederman" , Linus Torvalds , Andrew Morton , Arnd Bergmann , Tom Gundersen , Jiri Kosina , "linux-kernel@vger.kernel.org" , Daniel Mack , David Herrmann , Djalal Harouni Subject: Re: [GIT PULL] kdbus for 4.1-rc1 Message-ID: <20150415132018.GC2310@pd.tnic> References: <20150413190350.GA9485@kroah.com> <8738434yjk.fsf@x220.int.ebiederm.org> <20150413194217.GA10837@kroah.com> <20150413202233.GR889@ZenIV.linux.org.uk> <20150415084812.GG16381@kroah.com> <20150415122555.74258d63@lxorguk.ukuu.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150415122555.74258d63@lxorguk.ukuu.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1758 Lines: 43 On Wed, Apr 15, 2015 at 12:25:55PM +0100, One Thousand Gnomes wrote: > dbus is not an appropriate design for a kernel messaging layer for a > variety of reasons. That's not to say dbus shouldn't be able to use a > fast kernel messaging layer, or that one shouldn't exist. > > dbus is basically a very large very specialized and somewhat flawed > policy engine on top of what should be simple messaging. The two need > splitting apart. > > Abstract low level messaging layers are not a new concept. V7 unix had > one experimentally. It's about getting the separation right. > > IMHO that probably involves getting the right people in the right place > together - dbus designers, MPI and realtime people, kernel folks and > possibly also some of the hardware messaging folk. > > In filesystem terms > > - stop writing a dbus only file system > - figure out what a messaging "vfs" looks like > - figure out what an clean low level kernel model looks like > - figure out what has to be where to put the policy in userspace > > What might also be worth review is how much dbus traffic actually ought to > be an object store implemented say with tmpfs and inotify type > functionality (or extensions of that) so that you can > set/read/enumerate/get change notifications on properties. FWIW, this sounds really sane and makes a lot of sense to me. I'd be willing to give it some review cycles, as far as I can, when done this way. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- 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/