From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: Re: kdbus: add documentation Date: Sun, 30 Nov 2014 10:08:29 +0100 Message-ID: <87tx1hxdgy.fsf@mid.deneb.enyo.de> References: <1416546149-24799-1-git-send-email-gregkh@linuxfoundation.org> <1416546149-24799-2-git-send-email-gregkh@linuxfoundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Andy Lutomirski's message of "Fri, 21 Nov 2014 09:12:39 -0800") Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski Cc: Greg Kroah-Hartman , Arnd Bergmann , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Jiri Kosina , Linux API , "linux-kernel@vger.kernel.org" , Daniel Mack , David Herrmann , Djalal Harouni List-Id: linux-api@vger.kernel.org * Andy Lutomirski: > At the risk of opening a can of worms, wouldn't this be much more > useful if you could share a pool between multiple connections? They would also be useful to reduce context switches when receiving data from all kinds of descriptors. At present, when polling, you receive notification, and then you have to call into the kernel, again, to actually fetch the data and associated information. The kernel could also queue the data for one specific recipient, addressing the same issue that SO_REUSEPORT tries to solve (on poll notification, the kernel does not know which recipient will eventually retrieve the data, so it has to notify and wake up all of them). From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752191AbaK3JIq (ORCPT ); Sun, 30 Nov 2014 04:08:46 -0500 Received: from albireo.enyo.de ([46.237.207.196]:44405 "EHLO albireo.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751918AbaK3JIl (ORCPT ); Sun, 30 Nov 2014 04:08:41 -0500 From: Florian Weimer To: Andy Lutomirski Cc: Greg Kroah-Hartman , Arnd Bergmann , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Jiri Kosina , Linux API , "linux-kernel\@vger.kernel.org" , Daniel Mack , David Herrmann , Djalal Harouni Subject: Re: kdbus: add documentation References: <1416546149-24799-1-git-send-email-gregkh@linuxfoundation.org> <1416546149-24799-2-git-send-email-gregkh@linuxfoundation.org> Date: Sun, 30 Nov 2014 10:08:29 +0100 In-Reply-To: (Andy Lutomirski's message of "Fri, 21 Nov 2014 09:12:39 -0800") Message-ID: <87tx1hxdgy.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andy Lutomirski: > At the risk of opening a can of worms, wouldn't this be much more > useful if you could share a pool between multiple connections? They would also be useful to reduce context switches when receiving data from all kinds of descriptors. At present, when polling, you receive notification, and then you have to call into the kernel, again, to actually fetch the data and associated information. The kernel could also queue the data for one specific recipient, addressing the same issue that SO_REUSEPORT tries to solve (on poll notification, the kernel does not know which recipient will eventually retrieve the data, so it has to notify and wake up all of them).