Hi Thomas,
> -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, July 20, 2016 4:42 PM > To: Liang, Cunming <cunming.liang at intel.com> > Cc: Yong Wang <yongwang at vmware.com>; dev at dpdk.org; > david.marchand at 6wind.com > Subject: Re: [dpdk-dev] [PATCH] eal: fix rte_intr_dp_is_en() check > > 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. The EAL intr thread is reserved for all interrupt before, is not design for link interrupt on the first day. Personally I vote to remove link interrupt from interrupt thread. -Cunming
