From: Daniel Mack <daniel@zonque.org>
Subject: Re: kdbus: to merge or not to merge?
To: Andy Lutomirski <luto@amacapital.net>,
        David Herrmann <dh.herrmann@gmail.com>
References: <CALCETrW5sdcwM4zoX7BQdf+a2fWgQhd6rPDg8br0FU7Xy-2ZhQ@mail.gmail.com>
 <CALCETrVgot_QD2PC3rP4=ikOir4+A8T550aisLDoNkQMu93UtA@mail.gmail.com>
 <CANq1E4TL4goPTgTDaeQcu5qMwX9MCTN+emaGbSR7Y0ZUGJc_hw@mail.gmail.com>
 <CA+55aFzL93Vqa=a8eckOSReB_L4rX52v_7kcFNRFjkyA_fmd4w@mail.gmail.com>
 <CANq1E4SnYq_pZMWYcafB9GmB_O77tbVLPT0=0d6LGQVpvThTrw@mail.gmail.com>
 <CALCETrWE-oYRq+AzRxxcz03AK0pAzgKJtmxAuNwQu+p5S0msBw@mail.gmail.com>
 <CANq1E4Rek3HXCDU_13OGfRShS7Z0g+fxcTp5C1V3oKC4HgkD_A@mail.gmail.com>
 <CALCETrUaSgdaq4_mr3GG-ekLwGXkQR5MoRLSj9Wu2dTXDYUp1g@mail.gmail.com>
 <CANq1E4SkUWWXuksJnWzXd5KStZx-T6q6+WWTHdrQz_WiMry4Cw@mail.gmail.com>
 <CALCETrXcqOFedk8r-jHK-deRwfum29JHspALE6JUi2gzbo-dhg@mail.gmail.com>
Cc: Tom Gundersen <teg@jklm.no>, "Kalle A. Sandstrom" <ksandstr@iki.fi>,
        Greg KH <gregkh@linuxfoundation.org>, Borislav Petkov <bp@alien8.de>,
        One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
        Havoc Pennington <havoc.pennington@gmail.com>,
        Djalal Harouni <tixxdz@opendz.org>, cee1 <fykcee1@gmail.com>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Message-ID: <55C3A403.8020202@zonque.org>
Date: Thu, 6 Aug 2015 20:14:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CALCETrXcqOFedk8r-jHK-deRwfum29JHspALE6JUi2gzbo-dhg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1183
Lines: 31

On 08/06/2015 05:21 PM, Andy Lutomirski wrote:
> Maybe gdbus really does use kdbus already, but on
> very brief inspection it looked like it didn't at least on my test VM.

No, it's not in any released version yet. The patches for that are being
worked on though and look promising.

> If the client buffers on !EPOLLOUT and has a monster buffer, then
> that's the client's problem.
> 
> If every single program has a monster buffer, then it's everyone's
> problem, and the size of the problem gets multiplied by the number of
> programs.

The size of the memory pool of a bus client is chosen by the client
itself individually during the HELLO call. It's pretty much the same as
if the client allocated the buffer itself, except that the kernel does
it on their behalf.

Also note that kdbus features a peer-to-peer based quota accounting
logic, so a single bus connection can not DOS another one by filling its
buffer.


Thanks,
Daniel
--
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/