From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.20, mailfrom: maciej.rabeda@intel.com) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by groups.io with SMTP; Tue, 10 Sep 2019 05:50:18 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Sep 2019 05:50:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,489,1559545200"; d="scan'208";a="189332879" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by orsmga006.jf.intel.com with ESMTP; 10 Sep 2019 05:50:15 -0700 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.103]) by IRSMSX109.ger.corp.intel.com ([169.254.13.29]) with mapi id 14.03.0439.000; Tue, 10 Sep 2019 13:50:14 +0100 From: "Rabeda, Maciej" To: "devel@edk2.groups.io" , "rameshr@ami.com" CC: "Wu, Jiaxin" , "Fu, Siyuan" Subject: Re: Polling Interval in MNP Thread-Topic: Polling Interval in MNP Thread-Index: AdVnwy55ztWfhPFyQt2vZ/6AoFcgcwAEixwQ Date: Tue, 10 Sep 2019 12:50:14 +0000 Message-ID: <40FBBD5C52E8B4429773266A45BDCC174C65909A@IRSMSX104.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjljY2FlZmYtZjEwMS00NDU2LTkyZDktYmUzOTYyYzlhYjhkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoicDFzK1c2NlNBY3d6OHlMRmRkS3EzeHA4eEpRS0F2OFFqU2pYS1dpV3EwcUpjUGplRHEzZ01QaytjcUlPQ1poViJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [163.33.239.180] MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Ramesh, I cannot see the 10ms comparison you have mentioned in MnpCheckPacketTimeo= ut(). Quick code analysis suggests that received packets enqueued in the specifi= c MNP instance queue have timeout value assigned to them. See MnpQueueRcvdPacket() line: RxDataWrap->TimeoutTick =3D Instance->ConfigData.ReceivedQueueTimeoutValue= ; I believe that you can prevent packet timeout timer event from dropping th= ose packets by setting ReceivedQueueTimeoutValue to 0 upon calling MnpInsta= nce->Configure() function. Thanks! Maciej Rabeda -----Original Message----- From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Rame= sh R. Sent: Tuesday, September 10, 2019 12:34 To: 'devel@edk2.groups.io' Cc: Wu, Jiaxin ; Fu, Siyuan Subject: [edk2-devel] reg: Polling Interval in MNP Hi all: In the Network Package, MNPDxe Driver has the timeout check in MnpCheckPac= ketTimeout() for the interval of 10 ms. This interval is OK when we have th= e On board / Add on network controllers.=20 In the cases of Network devices exposed via Inband (Virtual USB exposing n= etwork interfaces) when there is a packet read given to USB interfaces and = it processed in lower level which could not provide the data within the 10 = ms interval and it failed with timeout and communication failed when we per= form the HTTP request. Do we have any specific reason to have this as 10 ms? Do we have any max l= imit for this interval value? Thanks, Ramesh -------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wyd= zial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-3= 16 | Kapital zakladowy 200.000 PLN. Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresat= a i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej w= iadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakie= kolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the = sole use of the intended recipient(s). If you are not the intended recipien= t, please contact the sender and delete all copies; any review or distribut= ion by others is strictly prohibited.