This change sysctlize last one of the parameter of if_em's interrupt moderation . sysctl hw.em?.int_throttle_ceil corresponds to the `absolute timer' at AP450(*1), application note by intel. *1 ftp://download.intel.com/design/network/applnots/ap450.pdf `absolute timer' is for suppressing rate of interrupt per unit of time. The value of int_throttle_ceil means a ceiling of the number of interrupt fireing per unit of time. Default value of int_throttle_ceil is 8000. Setting int_throttle_ceil 0 means disabling throttle moderation concerning the absolute timer. Fix: The diff of URL shown below adds sysctl int_throttle_ceil to hw.em?. http://www.fornext.org/patch/if_em.diff
Responsible Changed From-To: freebsd-bugs->tackerman Over to our Mr. em(4)
I'm sorry, there was a mistake in the description of int_throttle_ceil. int_throttle_ceil corresponds to the `throttle timer' at chapter 3.4 in AP450. -- Shunsuke SHINOMIYA <shino@fornext.org>
State Changed From-To: open->feedback Did this change ever get incorporated?
Responsible Changed From-To: tackerman->linimon Reset PR assigned to inactive committer. Hat: gnats-admin
----- Forwarded message from Shunsuke SHINOMIYA <shino@fornext.org> ----- From: Shunsuke SHINOMIYA <shino@fornext.org> To: Mark Linimon <linimon@FreeBSD.org> Thank you for your noticing. This patch has not been taken yet. And, I modified the patch for RELENG_6. http://www.fornext.org/patch/if_em_6.diff This function is useful for suppressing bursty traffic given by Interrupt Moderation. Thanks in advance. -- Shunsuke SHINOMIYA <shino@fornext.org> ----- End forwarded message -----
State Changed From-To: feedback->suspended The patch has not yet been incorporated. Mark 'suspended' awaiting an interested committer to evaluate.
Responsible Changed From-To: linimon->freebsd-bugs
Responsible Changed From-To: freebsd-bugs->glebius I will look at this.
Responsible Changed From-To: glebius->jfv Cleaning old PRs assigned to myself... Assign this one to the em(4) maintainer.
Reassign to erj@ for triage. To submitter: is this issue still relevant?
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
This is configured in supported versions via the sysctl: dev.em.0.itr: interrupt delay limit in usecs/4