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 D37DC211B696B for ; Tue, 29 Jan 2019 05:52:19 -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-us3.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 737FE6C006D; Tue, 29 Jan 2019 13:52:18 +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; Tue, 29 Jan 2019 05:52:14 -0800 To: Laszlo Ersek , "Fu, Siyuan" , "Wu, Jiaxin" , "edk2-devel@lists.01.org" CC: "Ye, Ting" References: <6029fb15-3820-0f05-f02a-577e99592bbc@solarflare.com> <32137552-e2b0-4392-17c7-dedaa1f05244@redhat.com> <09017041-d418-1186-9942-dfa70d82c4d6@solarflare.com> <67f8fb4a-5e1b-8bbc-90d4-670ff7e3bfe8@redhat.com> <5185c0b2-031f-ec50-b273-2665d83ef38a@solarflare.com> <923ebd9f-ef26-c96d-37cc-5cc76f88fea1@solarflare.com> <770c5b55-32b1-c2f3-f3de-b25de5f2b37d@solarflare.com> <841c4437-ad73-64d5-0eb8-cfc0220cc55d@solarflare.com> <895558F6EA4E3B41AC93A00D163B727416ECCDAA@SHSMSX107.ccr.corp.intel.com> <642a0352-e098-dc90-c9aa-89443a7dde04@solarflare.com> <8ef796a4-c3f1-d97a-03c8-add7ff6430b6@solarflare.com> <197303c9-8af5-6092-afe1-404cf86dd800@solarflare.com> <24080ea2-e564-69dd-73dd-ecbb5435f653@redhat.com> From: "Tomas Pilar (tpilar)" Message-ID: Date: Tue, 29 Jan 2019 13:52:11 +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: <24080ea2-e564-69dd-73dd-ecbb5435f653@redhat.com> X-Originating-IP: [10.17.20.51] X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24396.005 X-TM-AS-Result: No-18.757300-4.000000-10 X-TMASE-MatchedRID: 0dFPYP4mu5QOwH4pD14DsPHkpkyUphL9RWISSV5hxi/4JyR+b5tvoPhT 6/pHvNpJzX5RaqRCsDI202o65m3Ao6cSjSCV4bMxQC90vhPOlk3nSShdAiVGyvt592eq2xoT0Fi DqDlQgH7vVWUsZ2MpkhWo63MPPe/MQRHl12CcQN6AwosDBeuPwUGtrAxy5ENOFRlN8zTSzj5vAi 4DK4Hn3IlvNiK3d51FD73lcAnn23Il1ruS1vtrJZmug812qIbzLs/jKiF4CJh0cpXNtrVD/WRU7 /Hz0/OqJliIek/6y0ABhN609Bjwsn+q42d6CZjZr9glqbqf2bS0NJ9wxH7tk2HZ+cd7VyKXBu3i K2wia45r2PqlDE7ilca2bMMawhlOWsHLa0m5P00AWFA94fzR/0yQ5fRSh265IDM+GAqtbHImSkS BaVwPgWoyFBF/Gfm8vRKMIQgLHIKiRLBiOidj7Z4CIKY/Hg3AWQy9YC5qGvz6APa9i04WGCq2rl 3dzGQ1HhepeNBzEOHPeRlNwUJVpcs5REm8Q4hsRQr2q+zfrF8HaYoMCW3d4g== X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--18.757300-4.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24396.005 X-MDID: 1548769939-t6LO5-gAYuyv 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: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 X-List-Received-Date: Tue, 29 Jan 2019 13:52:20 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Language: en-US On 29/01/2019 13:42, Laszlo Ersek wrote: > On 01/29/19 11:54, Tomas Pilar (tpilar) wrote: >>> Why TFTP client just pull one packet per second? I think it’s not >>> correct and it could use the poll() function to accelerate the >>> receive. Why you trying to solve a TFTP layer problem in SNP layer? >>> It breaks the design principle of network layer model. >> Yes, I appreciate the principle. However, in practice we don't get to >> sell adapters that do not PXE boot and it's pointless to argue with >> customers that they have a rubbish TFTP client implementation. So we >> put in workarounds into the driver. > Actually, I think this is the core principle behind the UEFI forum, and > the UEFI spec. You shouldn't have to implement bug compat hacks. The era > when an add-on card would work on some platform's BIOS but not on > another's should be left behind. You have a spec to point at, and the > platform in question was likely certified against that spec in some form > (possibly self-certified). > > Sp I think it would be reasonable to contact the platform vendor, and to > direct your own customers to that ticket too. If you have a > representative on the USWG, it might make sense to raise the issue there > as well, especially if the issue is wide-spread and affects multiple > platform vendors. The UEFI spec targets practical, common use cases, and > this looks like one. > > (When a RH customer or partner reports e.g. a RHEL kernel issue to us, > and we determine it is a problem in the firmware, we absolutely talk to > the platform vendor, and sometimes to standards bodies too. We also > advise customers on the applications that they run on RHEL, if they ask > and/or care to listen. Plus, some high-profile applications and RHEL are > explicitly certified against each other.) > > ... I don't mean to intrude of course; I'm sorry if I came through like > that. Thanks, this is some good food for thought. I certainly appreciate the progress we've made since the old EFI days. Tom > > Thanks > Laszlo