[dpdk-dev] rte_panic SIGABRT core dump
Hi, Need help in avoiding core dump in case rte_eal_init() fails in some special cases. Part of my code causing rte_panic during system bootup and causes a core dump. I do not want this core dump. I tried catching SIGABRT in my application and did _exit() in my handler. Still I see core dump file getting generated. If I manually raise(SIGABRT) in my app, I do not see core dump. My SIGABRT handler not working if SIGABRT raised by rte_eal_init() and it causes core dump. Can someone help in avoiding core dump in case rte_eal_init() cause rte_panic. Thanks, Shiva
[dpdk-dev] rte_pmd_init_all is missing while upgrading from DPDK 1.6 to DPDK 1.7
Hi, I have rte_pmd_init_all used in my code. While upgrading from DPDK 1.6 to DPDK 1.7, I see this function is missing in DPDK 1.7. I removed rte_pmd_init_all from my code, but I am not sure whether initialization is done for all poll mode drivers What is the right way to do this?. Can anyone please help in this. Thanks, Shiva
[dpdk-dev] rte_pmd_init_all is missing while upgrading from DPDK 1.6 to DPDK 1.7
Hi, Thank you very much for your replies. I removed this API, I also see rte_eal_pci_set_blacklist() is no more available with DPDK 1.7.1, I am using rte_eal_devargs_add(). Any document mentioning changes from DPDK-1.6 to DPDK-1.7? Thanks, Shiva On Tue, May 24, 2016 at 11:32 AM, Wiles, Keith wrote: > The PMD?s are now being inited in the EAL init call for the code and that > API is not required anymore. If you are adding a new driver, make sure it > is up to date with any changes in the driver code too. > > Regards, > Keith > > > > >Hi, > > > >I have rte_pmd_init_all used in my code. While upgrading from DPDK 1.6 to > >DPDK 1.7, I see this function is missing in DPDK 1.7. I > >removed rte_pmd_init_all from my code, but I am not sure whether > >initialization is done for all poll mode drivers > > > >What is the right way to do this?. Can anyone please help in this. > > > >Thanks, > >Shiva > > > > > >