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: <20150424083501.GB7782@kroah.com>
Date:	Fri, 24 Apr 2015 10:35:01 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>, gnomes@...rguk.ukuu.org.uk,
	teg@...m.no, jkosina@...e.cz, luto@...capital.net,
	linux-kernel@...r.kernel.org, daniel@...que.org,
	dh.herrmann@...il.com, tixxdz@...ndz.org
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

On Fri, Apr 24, 2015 at 08:45:15AM +0200, Greg Kroah-Hartman wrote:
> On Fri, Apr 24, 2015 at 08:36:03AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Apr 23, 2015 at 10:56:40PM +0200, Borislav Petkov wrote:
> > > > Hm, this seems to be to be O(1), pretty constant, we do the same amount
> > > > of work all the time.
> > > 
> > > The same *pile* of unnecessary and needless work. You go and collect
> > > *all* that data on *every* packet send?!
> > 
> > No, not at all, the metadata is cached, we only collect that for the
> > first message sent, if we didn't know it already, or we do it on the
> > "open" of the connection, depending on what we are gathering metadata
> > for.
> > 
> > The mc->collected test right before collecting the specific metadata is
> > that "cached or not" test.
> 
> Oh wait, no, there are some send-time metadata that is collected for
> every message, see Linus's email for more details about that.  Maybe
> this can be changed to cache things even more than we currently do.
> 
> it's early, shouldn't write emails before coffee...
> 
> David had some flamegraphs floating around that showed where all the
> time on transmit / receive was being spent, and I don't think that the
> metadata area was all that relevant, but I can't find them anymore to
> say for sure.  There are other areas that can be sped up on the send
> path, but perf data is the best way to verify this.

Here's the graphs that he posted during the last code review cycle that
are relevant here:
	http://lkml.iu.edu/hypermail/linux/kernel/1503.2/02624.html

greg k-h
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ