linux-kernel - Re: [GIT PULL] kdbus for 4.1-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1506222223040.20625@twin.jikos.cz>
Date:	Mon, 22 Jun 2015 22:23:56 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jindrich Makovicka <makovick@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

On Mon, 22 Jun 2015, Jindrich Makovicka wrote:

> >> IOW, all the people who say that it's about avoiding context switches
> >> are probably just full of shit. It's not about context switches, it's
> >> about bad user-level code.
> > 
> > Just to make sure, I did a system-wide profile (so that you can actually
> > see the overhead of context switching better), and that didn't change
> > the picture.
> > 
> > The scheduler overhead *might* be 1% or so.
> > 
> > So really. The people who talk about how kdbus improves performance are
> > just full of sh*t. Yes, it improves things, but the improvement seems to
> > be 100% "incidental", in that it avoids a few trips down the user-space
> > problems.
> > 
> > The real problems seem to be in dbus memory management (suggestion: keep
> > a small per-thread cache of those message allocations) and to a smaller
> > degree in the crazy utf8 validation (why the f*ck does it do that
> > anyway?), with some locking problems thrown in for good measure.
> 
> In case someone actually still reads this, I guess the global rw_lock in 
> gobject/gtype.c is one of the culprits. Every GType instance allocation/
> deallocation is serialized using this lock, which pretty much 
> disqualifies GObject from being used for anything scalable to multiple 
> threads.
> 
> GStreamer used to have serious performance issues due to that, which 
> AFAIK have been solved by removing GType from GStreamer core in the 1.0 
> release.

This is interesting piece of information, but you unfortunately dropped 
everybody from CC, so it's very likely that it's going to be lost in the 
noise.

Could you please resend with CC list restored?

Thanks,

-- 
Jiri Kosina
SUSE Labs

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/