From: Christian Melki <christian.melki@t2data.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] No link up before IFF_UP? (early link optimization)
Date: Wed, 13 Apr 2022 08:10:47 +0200 [thread overview]
Message-ID: <3438c789-d4c2-1b41-79d2-d2fb9ff6f089@t2data.com> (raw)
I have a optimization task for a time constrained boot process.
The system in question is an AMD Ryzen from the R1000 family with an
Intel I211 running igb in 5.17.1.
The current kernel and driver behavior:
UEFI (link up) -> Kernel starts, driver is probed (link down) -> link
stays down until userspace IFF_UP -> after an extra +6-7 seconds the
link comes up.
This means that the userspace can't start communication after 6-7
seconds after device open. Moving the interface initialization earlier
won't help much as IFF_UP is about 0.5 away from jumping to initramfs.
So the question is: Can I get the interface to stop powering down after
probe? If reset is needed, then take up the interface again. Of course
the kernel won't start forwarding until netif_carrier transitions.
But I'd like to move the resets and powerups as early as possible.
I guess that also means no resets if no settings have changed.
Regards,
Christian
reply other threads:[~2022-04-13 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3438c789-d4c2-1b41-79d2-d2fb9ff6f089@t2data.com \
--to=christian.melki@t2data.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox