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>] [day] [month] [year] [list]
Message-ID: <CAJ2oMhJDhX89ja2zzz_UomHquhiy+OqFgco6Hgora6KPiUSK1A@mail.gmail.com>
Date:   Thu, 29 Mar 2018 19:20:34 +0300
From:   Ran Shalit <ranshalit@...il.com>
To:     netdev@...r.kernel.org
Subject: Reduce boot time till ping

Hello,

I'm struggling to understand why it takes a lot of time to boot till
we get ping success.
We use system with i210 , and igb driver.
I use dmesg for time measurement( and gpios to sync dmesg timing with
board power time)

This is dmesg with added prints for each IGB function enter and exit time:
https://drive.google.com/file/d/1Zdxp_fljawrzpuM4Q0at5YH6yOahoSse/view?usp=sharing

I see that driver use some watchdog to decide if link is up (as can be
seen in the above log), yet I don't understand why it takes so long
from kernel start till ping success.

Even when link is up it still take a long interval from link up till
ping success, as you can see in the log file.


I can't disable auto-negotiation because we need to use 1Gb.
Is there anything else I can do ?

Thank you,
ranran

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ