Re: [arch-projects] [netcfg] Call for testers: netctl
Running v0.1-1 here with a static config and it seems to be working just fine. One thing I will report is that it starts a bit slower than netcfg: % systemd-analyze blame 3396ms netcfg.service % systemd-analyze blame 4076ms netctl@static.service Can you inspect my profile and suggest an optimization? Thank you. This looks like the beginnings of a great project by the way. % cat /etc/network.d/static Connection=ethernet Interface=eth0 BindToInterfaces=(eth0) ExecUpPost='/usr/sbin/ip link set eth0 mtu 4000' ExecDownPre='/usr/bin/pkill sshd' IP=static Address=10.1.10.101 Gateway=10.1.10.1 DNS=('10.1.10.1')
On Mon, Dec 31, 2012 at 3:13 PM, member graysky <graysky@archlinux.us> wrote:
Running v0.1-1 here with a static config and it seems to be working just fine. One thing I will report is that it starts a bit slower than netcfg:
% systemd-analyze blame 3396ms netcfg.service
% systemd-analyze blame 4076ms netctl@static.service
Can you inspect my profile and suggest an optimization? Thank you. This looks like the beginnings of a great project by the way.
Are these results structural? You should probably compare netctl@static to netcfg@static, but other than that I would expect not much of a difference. The control flow is very similar, with a preference for netctl, as (I think) it will do less function calls. Also, keep in mind that due to parallelization, these timings are not extremely important. The difference is strange, though. It might be openresolv that takes a bit longer than writing to resolv.conf directly, but 700ms seems a bit much.
% cat /etc/network.d/static Connection=ethernet Interface=eth0 BindToInterfaces=(eth0)
This line is not needed, as $BindToInterfaces defaults to $Interface.
ExecUpPost='/usr/sbin/ip link set eth0 mtu 4000' ExecDownPre='/usr/bin/pkill sshd'
IP=static Address=10.1.10.101 Gateway=10.1.10.1 DNS=('10.1.10.1')
Regards, - Jouke
On Mon, Dec 31, 2012 at 1:51 PM, Jouke Witteveen <j.witteveen@gmail.com> wrote:
Are these results structural? You should probably compare netctl@static to netcfg@static, but other than that I would expect not much of a difference. The control flow is very similar, with a preference for netctl, as (I think) it will do less function calls. Also, keep in mind that due to parallelization, these timings are not extremely important. The difference is strange, though. It might be openresolv that takes a bit longer than writing to resolv.conf directly, but 700ms seems a bit much.
% cat /etc/network.d/static Connection=ethernet Interface=eth0 BindToInterfaces=(eth0)
This line is not needed, as $BindToInterfaces defaults to $Interface.
OK! I'm not sure what you mean by 'structural' but after a reboot, it seems that the times are much closer to each other now: % systemd-analyze blame 3479ms netctl@static.service Also, thanks for the suggestion about the profile. I too like the interface you have designed and hope others agree. Keep up the excellent start you've made with netctl!
ethernet-{static,dhcp} works just fine :) Haven't tested other profiles yet.
participants (3)
-
Axilleas Pi
-
Jouke Witteveen
-
member graysky