From: Laszlo Ersek <lersek@redhat.com>
To: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>, edk2-devel@lists.01.org
Subject: Re: Network Stack Budgeting
Date: Thu, 24 Jan 2019 17:49:07 +0100 [thread overview]
Message-ID: <f4e271da-7d5b-0583-3f33-0f65020d92e1@redhat.com> (raw)
In-Reply-To: <770c5b55-32b1-c2f3-f3de-b25de5f2b37d@solarflare.com>
On 01/24/19 14:25, Tomas Pilar (tpilar) wrote:
> Hmm,
>
> Mnp->Configure() will eventually call MnpStartSnp().
>
> A grep for Mnp->Configure shows that:
> * ArpDxe performs this on DriverBinding.Start()
> * Ip6Dxe performs this on DriverBinding.Start()
>
> Ipv4 and DnsDhcp do this as a part of their Configure() they expose in the API.
Yes, that makes sense. All of the above drivers are UEFI drivers that
follow the UEFI driver model, AIUI. As long as the controller is not
connected from BDS, no BindingStart() function should be called in these.
E.g. EFI_DNS4_PROTOCOL.Configure() can only be called if an instance of
that protocol exists (... for the NIC in question), but the protocol
instance won't exist unless BDS (or some other agent such as the shell
or the boot menu app) called ConnectController().
Thanks,
Laszlo
next prev parent reply other threads:[~2019-01-24 16:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 10:55 Network Stack Budgeting Tomas Pilar (tpilar)
2019-01-23 14:14 ` Ye, Ting
2019-01-23 14:51 ` Tomas Pilar (tpilar)
2019-01-23 16:08 ` Laszlo Ersek
2019-01-23 16:27 ` Tomas Pilar (tpilar)
2019-01-23 17:47 ` Andrew Fish
2019-01-23 22:18 ` Laszlo Ersek
2019-01-24 11:37 ` Tomas Pilar (tpilar)
2019-01-24 12:25 ` Laszlo Ersek
2019-01-24 12:58 ` Tomas Pilar (tpilar)
2019-01-24 13:25 ` Tomas Pilar (tpilar)
2019-01-24 16:49 ` Laszlo Ersek [this message]
2019-01-24 17:43 ` Tomas Pilar (tpilar)
2019-01-25 8:44 ` Wu, Jiaxin
2019-01-25 12:08 ` Tomas Pilar (tpilar)
2019-01-27 14:28 ` Fu, Siyuan
2019-01-28 11:24 ` Tomas Pilar (tpilar)
2019-01-29 3:20 ` Fu, Siyuan
2019-01-29 10:54 ` Tomas Pilar (tpilar)
2019-01-29 13:06 ` Fu, Siyuan
2019-01-29 13:12 ` Tomas Pilar (tpilar)
2019-01-29 13:42 ` Laszlo Ersek
2019-01-29 13:52 ` Tomas Pilar (tpilar)
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-list 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=f4e271da-7d5b-0583-3f33-0f65020d92e1@redhat.com \
--to=devel@edk2.groups.io \
/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