From: Bruce Richardson <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: [PATCH 0/3] eal affinitize low priority threads to lcore 0
Date: Thu, 11 Sep 2014 15:23:04 +0100 [thread overview]
Message-ID: <1410445387-4849-1-git-send-email-bruce.richardson@intel.com> (raw)
This patchset sets things up so that we can affinitize the interrupt,
vfio management, and hpet timer management threads to lcore 0, so that
they never interfere with data plane threads.
Bruce Richardson (3):
eal: add core id param to eal_thread_set_affinity
eal: increase scope of eal_thread_set_affinity
eal: affinitize low-priority threads to lcore 0
lib/librte_eal/bsdapp/eal/eal_thread.c | 12 ++++++------
lib/librte_eal/common/include/eal_private.h | 10 ++++++++++
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 5 +++++
lib/librte_eal/linuxapp/eal/eal_pci_vfio_mp_sync.c | 6 ++++++
lib/librte_eal/linuxapp/eal/eal_thread.c | 12 ++++++------
lib/librte_eal/linuxapp/eal/eal_timer.c | 5 +++++
6 files changed, 38 insertions(+), 12 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-11 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 14:23 Bruce Richardson [this message]
[not found] ` <1410445387-4849-1-git-send-email-bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-11 14:23 ` [PATCH 1/3] eal: add core id param to eal_thread_set_affinity Bruce Richardson
2014-09-11 14:23 ` [PATCH 2/3] eal: increase scope of eal_thread_set_affinity Bruce Richardson
2014-09-11 14:23 ` [PATCH 3/3] eal: affinitize low-priority threads to lcore 0 Bruce Richardson
2014-09-11 23:47 ` [PATCH 0/3] eal affinitize low priority " Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD011AC7A6-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-09-12 1:24 ` Stephen Hemminger
2014-09-12 8:07 ` Richardson, Bruce
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=1410445387-4849-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).