Hi Ting, Currently we see it on DELL 13G platforms. However, in my experience most platforms will call Snp.Start() immediatelly following the ConnectController() way before the boot manager is entered.
Cheers, Tom On 23/01/2019 14:14, Ye, Ting wrote: > Hi Tom, > > As I known it is up to platform BDS when to connect network stack, or even > not to connect network stack. For example, in fast boot process, network > stack will not be connected thus Snp.Start() has no chance to be called. > May I know which platforms you see this issue? > > Thanks, > Ting > > > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Tomas > Pilar (tpilar) > Sent: Wednesday, January 23, 2019 6:56 PM > To: edk2-devel@lists.01.org > Subject: [edk2] Network Stack Budgeting > > Hi, > > Recently I have done some performance improvements to my network driver. I am > however finding that on some platforms, it's becoming impossible to boot if > the network cable has a lot of traffic on it that is not filtered by the NIC > itself (broadcast, multicast or directed unicast). It would seem the platform > hangs in the DXE phase trying to process (drop) all the packets and not > progressing through the boot order. > > I am wondering if anyone has seen similar behaviour. Does the network stack > have any budgeting? > > Ideally this would be fixed by the network stack not calling Snp.Start() > until in the BDS phase but it seems most platforms just call Snp.Start() > immediately following the driver probe. > > Cheers, > Tom > > > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
