Re: [systemd-devel] Hashmap iteration is too costly

2017-07-17 Thread vcaputo
On Mon, Jul 17, 2017 at 10:12:12AM +0200, Lennart Poettering wrote: > On Fri, 14.07.17 03:18, vcap...@pengaru.com (vcap...@pengaru.com) wrote: > > > The current hashmap iteration incurs at least one function call per > > iteration, and in my observations using gcc 6.3 w/-g -O2, it's two: > > > >

Re: [systemd-devel] Hashmap iteration is too costly

2017-07-17 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Jul 17, 2017 at 10:12:12AM +0200, Lennart Poettering wrote: > On Fri, 14.07.17 03:18, vcap...@pengaru.com (vcap...@pengaru.com) wrote: > > > The current hashmap iteration incurs at least one function call per > > iteration, and in my observations using gcc 6.3 w/-g -O2, it's two: > > > >

[systemd-devel] systemd-nspawn network-interface doesn't return interface on container reboot

2017-07-17 Thread Dmitry Kulida
Hi Everyone. I have below trouble. I start my container with --network-interface option as below: ExecStart=/usr/bin/systemd-nspawn -M %i.%H --quiet --keep-unit --boot --link-journal=auto --network-veth *--network-interface=dummy6* --capability=CAP_NET_RAW --directory=/var/lib/container/%i

Re: [systemd-devel] Hashmap iteration is too costly

2017-07-17 Thread Lennart Poettering
On Fri, 14.07.17 03:18, vcap...@pengaru.com (vcap...@pengaru.com) wrote: > The current hashmap iteration incurs at least one function call per > iteration, and in my observations using gcc 6.3 w/-g -O2, it's two: > > internal_hashmap_iterate() > hashmap_iterate_entry() > > for every element

Re: [systemd-devel] Realtime scheduling with CONFIG_RT_GROUP_SCHED=y

2017-07-17 Thread Lennart Poettering
On Wed, 12.07.17 11:41, Lars Kellogg-Stedman (l...@redhat.com) wrote: > On Thu, Jul 6, 2017 at 10:56 AM, Lars Kellogg-Stedman > wrote: > > > In older versions of systemd one could handle this using the directives > > described in