From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=67.231.154.164; helo=dispatch1-us1.ppe-hosted.com; envelope-from=tpilar@solarflare.com; receiver=edk2-devel@lists.01.org Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 95848211B6C23 for ; Wed, 23 Jan 2019 06:51:27 -0800 (PST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (webmail.solarflare.com [12.187.104.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id EFB03140058; Wed, 23 Jan 2019 14:51:25 +0000 (UTC) Received: from tp-desktop.uk.solarflarecom.com (10.17.20.51) by ocex03.SolarFlarecom.com (10.20.40.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 23 Jan 2019 06:51:22 -0800 To: "Ye, Ting" , "edk2-devel@lists.01.org" References: <6029fb15-3820-0f05-f02a-577e99592bbc@solarflare.com> From: "Tomas Pilar (tpilar)" Message-ID: <9c03a4db-821d-9d15-a54d-a3eb1345bda3@solarflare.com> Date: Wed, 23 Jan 2019 14:51:21 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.17.20.51] X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24384.005 X-TM-AS-Result: No-20.026200-4.000000-10 X-TMASE-MatchedRID: u7Yf2n7Ca/3hvc6DRV+j7Res/RxhysDbMUUuEZQPwBYNcckEPxfz2AQ9 n8U23GDf3f0e/BgwI9BOgbtC40Xi2RxOqdFMk/f/jhXy0Khej9IF15s6prCIu45t/XRqktxJXa2 +zE1cP+U3jelxKeBccK/6/0DnZa3nfNMhSGKNK0ZTdqZ2L9mRu0yNDX2PfTDJ5DJ1FS+XdBM/pX tfNEiQBhMmCybjlFENvJxmDUgAiKaFgI8rbWwRO4GU23hVIa8hIZm2INWXDp7RZJBIXaKMIL/4E fC9QJBNj1mbw6/tKms/Ic8ea6pSaBgHZ8655DOPOX/V8P8ail1ZDL1gLmoa/PoA9r2LThYYKrau Xd3MZDU980qe9xzB3A== X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--20.026200-4.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24384.005 X-MDID: 1548255086-hTgHLuG8pMam Subject: Re: Network Stack Budgeting X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2019 14:51:27 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Language: en-US 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-bounces@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