From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: dev@dpdk.org, Nirranjan Kirubaharan <nirranjan@chelsio.com>,
Felix Marti <felix@chelsio.com>,
Kumar Sanghvi <kumaras@chelsio.com>
Subject: Re: [dpdk-dev] Recent changes related to interrupt thread
Date: Mon, 16 Nov 2015 14:48:42 +0100 [thread overview]
Message-ID: <8192567.2fdTdH6sjP@xps13> (raw)
In-Reply-To: <20151116123200.GA2667@scalar.blr.asicdesigners.com>
Hi,
2015-11-16 18:02, Rahul Lakkireddy:
> Hi,
>
> I notice that the following changeset:
>
> Fixes: fd6949c55c9a ("eal: fix io permission for virtio interrupt
> handler")
>
> has moved the initialization of the interrupt thread to after the master
> lcore has been initialized. However, this causes the interrupt thread
> to _inherit_ the affinity of the master lcore. Hence, this seems to
> make all interrupts to be handled by _only_ the master lcore. Because
> of this change, it seems that now alarm interrupts would also be handled
> by master lcore only, IIUC.
>
> We are seeing a performance regression for cxgbe PMD after this commit
> since, cxgbe PMD relies on alarm to periodically transmit pending
> coalesced packets.
>
> Also, this perf degradation is only seen if there's a queue allocated
> on the master lcore, such as in l3fwd app. If the master lcore has
> been skipped, then no degradation in perf is seen since only the alarm
> will run on the master lcore.
>
> So, is the change done to make all interrupts, including alarm
> interrupts, be handled by _only_ the master lcore intended?
No it was not intended. The idea was to inherit settings (iopl) from
the device initialization into the interrupt thread.
Though a DPDK driver is not really supposed to rely on interrupt performance.
So having interrupts managed on any core was more or less a side effect.
> BTW, I have tried setting the affinity to all cpus instead in
> eal_intr_init() and this seems to restore the perf back. Perhaps it's
> better to move the master lcore initialization to after the interrupt
> thread has been initialized as well? Thoughts?
Yes, i think it's possible.
We can also imagine a command line option to set the interrupt affinity
with a default which mimics the old behaviour.
In order to make this conversation clearer, and for later references,
below is the DPDK init call tree:
start
driver constructor (if .a)
rte_eal_driver_register
main
rte_eal_init
eal_parse_args
rte_eal_pci_init
rte_eal_memory_init
eal_plugins_init
dlopen
driver constructor (if .so)
rte_eal_driver_register
eal_thread_init_master
eal_thread_set_affinity
rte_eal_dev_init
driver->init
PMD init
rte_eth_driver_register
rte_eal_intr_init
pthread_create
eal_intr_thread_main
eal_intr_handle_interrupts
pthread_create
rte_eal_pci_probe
driver->devinit
rte_eth_dev_init
rte_eth_dev_allocate
eth_drv->eth_dev_init
next prev parent reply other threads:[~2015-11-16 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:32 Rahul Lakkireddy
2015-11-16 13:48 ` Thomas Monjalon [this message]
2015-11-16 17:06 ` Stephen Hemminger
2015-11-16 17:19 ` Ananyev, Konstantin
2015-11-16 17:40 ` Stephen Hemminger
[not found] ` <2601191342CEEE43887BDE71AB97725836AC98E9@irsmsx105.ger.corp.intel.com>
2015-11-17 11:48 ` Ananyev, Konstantin
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=8192567.2fdTdH6sjP@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=felix@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
/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).