From: Joe Buehler <aspam@cox.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] ixgbevf RX latency outliers
Date: Mon, 04 Dec 2017 16:41:15 -0500 [thread overview]
Message-ID: <5A25C0FB.10006@cox.net> (raw)
I am using the ixgbevf driver shipped with the 4.4.86 LINUX
realtime-patched kernel in a VM using SRIOV.
The kernel is timestamping incoming frames and in general is doing a
great job but I am having some difficulties with RX latency outliers.
Presumably something is not servicing the NIC in a timely fashion, or
the NIC is holding on to frames too long. I am looking for some info on
the design of the driver, the intent being perhaps to change NIC config,
revise RT priorities and/or thread affinities.
There appear to be 3 IRQ threads for example -- what are they for?
Any help much appreciated.
Joe
reply other threads:[~2017-12-04 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=5A25C0FB.10006@cox.net \
--to=aspam@cox.net \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.