On 1/30/2018 8:14 AM, Thomas Monjalon wrote:
27/01/2018 04:48, Guo, Jia:
On 1/27/2018 12:53 AM, Bruce Richardson wrote:
On Fri, Jan 26, 2018 at 11:49:35AM +0800, Jeff Guo wrote:
+ ret = rte_service_lcore_add(slcore);
+ if (ret) {
+ RTE_LOG(ERR, EAL, "dev event monit
27/01/2018 04:48, Guo, Jia:
> On 1/27/2018 12:53 AM, Bruce Richardson wrote:
> > On Fri, Jan 26, 2018 at 11:49:35AM +0800, Jeff Guo wrote:
> >> + ret = rte_service_lcore_add(slcore);
> >> + if (ret) {
> >> + RTE_LOG(ERR, EAL, "dev event monitor lcore add fail");
> >> + return re
On 1/27/2018 12:53 AM, Bruce Richardson wrote:
On Fri, Jan 26, 2018 at 11:49:35AM +0800, Jeff Guo wrote:
This patch aim to add a general uevent mechanism in eal device layer,
to enable all linux kernel object uevent monitoring, user could use these
APIs to monitor and read out the device statu
On Fri, Jan 26, 2018 at 11:49:35AM +0800, Jeff Guo wrote:
> This patch aim to add a general uevent mechanism in eal device layer,
> to enable all linux kernel object uevent monitoring, user could use these
> APIs to monitor and read out the device status info that sent from the
> kernel side, then
This patch aim to add a general uevent mechanism in eal device layer,
to enable all linux kernel object uevent monitoring, user could use these
APIs to monitor and read out the device status info that sent from the
kernel side, then corresponding to handle it, such as when detect hotplug
uevent typ
This patch aim to add a general uevent mechanism in eal device layer,
to enable all linux kernel object uevent monitoring, user could use these
APIs to monitor and read out the device status info that sent from the
kernel side, then corresponding to handle it, such as when detect hotplug
uevent typ
6 matches
Mail list logo
