public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Siyuan, Fu" <siyuan.fu@intel.com>
To: Sivaraman Nainar <sivaramann@amiindia.co.in>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wu, Jiaxin" <jiaxin.wu@intel.com>
Subject: Re: Polling Interval in MNP
Date: Sat, 14 Sep 2019 02:54:09 +0000	[thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B863EFE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <B4DE137BDB63634BAC03BD9DE765F197028B28FD17@VENUS1.in.megatrends.com>

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

Hi, Siva

The 10ms interval was chosen just by experience. This background polling intends to pick up the coming request (e.g. ARP request) when there is no active polling from upper layer. The ARP time out is 1 second, so using 10ms background polling make the network stack able to receive ARP request among 100 incoming package/second.

You can change this to a reasonable time for the inband network.

Best Regards
Siyuan

From: Sivaraman Nainar <sivaramann@amiindia.co.in>
Sent: 2019年9月10日 17:17
To: devel@edk2.groups.io
Cc: Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>
Subject: reg: Polling Interval in MNP

Hi all:

In the Network Package, MNPDxe Driver has the timeout check in MnpCheckPacketTimeout() for the interval of 10 ms. This interval is OK when we have the On board / Add on network controllers.

In the cases of Network devices exposed via Inband (Virtual USB exposing network 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 perform the HTTP request.

Do we have any specific reason to have this as 10 ms? Do we have any max limit for this interval value?

-Siva

[-- Attachment #2: Type: text/html, Size: 4950 bytes --]

       reply	other threads:[~2019-09-14  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B4DE137BDB63634BAC03BD9DE765F197028B28FD17@VENUS1.in.megatrends.com>
2019-09-14  2:54 ` Siyuan, Fu [this message]
2019-09-10 10:34 reg: Polling Interval in MNP Ramesh R.
2019-09-10 12:50 ` Rabeda, Maciej

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=B1FF2E9001CE9041BD10B825821D5BC58B863EFE@SHSMSX103.ccr.corp.intel.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