[prev in list] [next in list] [prev in thread] [next in thread] 

List:       systemd-devel
Subject:    Re: [systemd-devel] bus benchmark
From:       Lennart Poettering <lennart () poettering ! net>
Date:       2018-03-28 10:41:00
Message-ID: 20180328104100.GB6118 () gardel-login
[Download RAW message or body]

On Di, 27.03.18 22:24, zhiting zhu (zhitingz@cs.utexas.edu) wrote:

> Hi,
> 
> I have a question about the bus benchmark. On the v238, the benchmark only
> works with the input chart direct. If I put another input, the program gets
> an assertion failure. Also, what chart, bisec, legacy, direct means?
> There's no documentation come with the benchmark. I wonder what that output
> means? What metric does it try to show? Is this a latency or throughput
> benchmark?

That tool was written in order to determine when transport via memfd
would be faster than transport via AF_UNIX datagrams. i.e. the
datagram size at which point zero-copy transport (which implies
mmap()ing) becomes more efficient than copy-based transports.

If you so will it's a remnant of the kdbus experiments, and we should
probably remove it from the tree.

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[prev in list] [next in list] [prev in thread] [next in thread]