From: "terry.montague.1980@btinternet.com" <terry.montague.1980@btinternet.com>
To: users@dpdk.org
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Linux descheduling DPDK transmit thread in SMP system? Any help greatly appreciated...
Date: Wed, 6 Sep 2017 08:48:58 +0100 (BST) [thread overview]
Message-ID: <31543919.4352.1504684138463.JavaMail.defaultUser@defaultHost> (raw)
In-Reply-To: <20170905095552.53cfcd17@xeon-e3>
Stephen - thank-you for your input.
Tens of milliseconds seems an awful long time for some kernel-side resource lock, although its obviously doing something with the time. There is only one user thread running on this core (my transmit thread).
Does anyone have an approach to suggest to narrow this down a bit? Would I expect this to be worse on an SMP system?
Many thanks
Terry.
----Original message----
>From : stephen@networkplumber.org
Date : 05/09/17 - 17:55 (BST)
To : terry.montague.1980@btinternet.com
Cc : users@dpdk.org
Subject : Re: [dpdk-users] Linux descheduling DPDK transmit thread in SMP system? Any help greatly appreciated...
On Tue, 5 Sep 2017 17:35:16 +0100 (BST)
"terry.montague.1980@btinternet.com" <terry.montague.1980@btinternet.com> wrote:
> Hi all,
> I'm running a DPDK transmit thread with the ixgbe PMD on Ubuntu 17.04, with dual Xeon E5-2623 v4 CPUs on an Intel S2600 motherboard. The cores in use by DPDK are isolated in the boot cmdline with "isolcpus"
> What I'm observing is I believe, on occasion, the DPDK transmit thread being descheduled by the system for between 20 and 60 milliseconds.
> I've tried running as Real time with max priority, and tweaking the scheduling through /proc/sys/kernel/sched_rt_runtime_us to be 99.999% available for real time thread, but so far no improvement
> I notice there are various kernel threads resident on the isolated cpus, cpuhp/watchdog/migration/ksoftirqd +multiple kworker threads.
> I can only assume the system is occasionally running these kernel side instead, although the CPU time taken (tens of milliseconds) seems very high. Note please that I amd NOT running with a modified kernel (nohz_full is not set).
> Does anyone have any advice to keep the DPDK transmit thread running for more of the time on this SMP system ?
> Many thanks
> Terry.
Probably not a Linux scheduler issue. More likely some system hardware thing like SMT or ME.
next prev parent reply other threads:[~2017-09-06 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 16:35 terry.montague.1980
2017-09-05 16:55 ` Stephen Hemminger
2017-09-06 7:48 ` terry.montague.1980 [this message]
2017-09-06 15:16 ` Stephen Hemminger
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=31543919.4352.1504684138463.JavaMail.defaultUser@defaultHost \
--to=terry.montague.1980@btinternet.com \
--cc=users@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).