[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzL93Vqa=a8eckOSReB_L4rX52v_7kcFNRFjkyA_fmd4w@mail.gmail.com>
Date: Tue, 4 Aug 2015 06:46:03 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Herrmann <dh.herrmann@...il.com>
Cc: Andy Lutomirski <luto@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Djalal Harouni <tixxdz@...ndz.org>,
Greg KH <gregkh@...uxfoundation.org>,
Havoc Pennington <havoc.pennington@...il.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Daniel Mack <daniel@...que.org>,
"Kalle A. Sandstrom" <ksandstr@....fi>,
Borislav Petkov <bp@...en8.de>, cee1 <fykcee1@...il.com>
Subject: Re: kdbus: to merge or not to merge?
On Tue, Aug 4, 2015 at 1:58 AM, David Herrmann <dh.herrmann@...il.com> wrote:
>
> You lack a call to sd_bus_unref() here.
I assume it was intentional. Why would Andy talk about "scaling" otherwise?
And the worry was why the kdbus version killed the machine, but the
userspace version did not. That's a rather big difference, and not a
good one.
Possibly the kdbus version ends up not just allocating user space
memory (which we should handle gracefully), but kernel allocations too
(which absolutely have to be explicitly resource-managed).
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists