From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Liang, Cunming" <cunming.liang@intel.com>
Cc: Yong Wang <yongwang@vmware.com>,
dev@dpdk.org,
"david.marchand@6wind.com" <david.marchand@6wind.com>
Subject: Re: [PATCH] eal: fix rte_intr_dp_is_en() check
Date: Wed, 20 Jul 2016 10:41:56 +0200 [thread overview]
Message-ID: <2847845.SJj9hZrsaB@xps13> (raw)
In-Reply-To: <D0158A423229094DA7ABF71CF2FA0DA31554AE03@shsmsx102.ccr.corp.intel.com>
2016-07-20 07:03, Liang, Cunming:
> Probably a clean way is not to handle device external interrupt event in EAL
> interrupt thread (intr mb may have some problem). The EAL interrupt thread is
> only used to postpone the delay execution or other background interrupt
> (e.g. alarm). Then misc/non-misc can be combined, while requiring APP to
> detect the interrupt causes.
I am not sure it was a good idea to have a thread for the link interrupt.
It may be simpler and cleaner to let the application do the pthread_create.
next prev parent reply other threads:[~2016-07-20 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 0:36 [PATCH] eal: fix rte_intr_dp_is_en() check Yong Wang
2016-07-18 6:19 ` Liang, Cunming
2016-07-18 9:21 ` Thomas Monjalon
2016-07-19 21:58 ` Yong Wang
2016-07-20 7:03 ` Liang, Cunming
2016-07-20 8:41 ` Thomas Monjalon [this message]
2016-07-20 8:56 ` Liang, Cunming
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=2847845.SJj9hZrsaB@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cunming.liang@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=yongwang@vmware.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 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.