thanks for your review. please check v13.
On 1/24/2018 10:52 PM, Wu, Jingjing wrote:
-Original Message-
From: Guo, Jia
Sent: Thursday, January 18, 2018 12:12 PM
To: step...@networkplumber.org; Richardson, Bruce ;
Yigit, Ferruh ; gaetan.ri...@6wind.com
Cc: Ananyev, Konstantin ; jblu...@
> -Original Message-
> From: Guo, Jia
> Sent: Thursday, January 18, 2018 12:12 PM
> To: step...@networkplumber.org; Richardson, Bruce
> ;
> Yigit, Ferruh ; gaetan.ri...@6wind.com
> Cc: Ananyev, Konstantin ; jblu...@infradead.org;
> shreyansh.j...@nxp.com; Wu, Jingjing ; dev@dpdk.org;
>
On 1/19/2018 9:13 AM, Thomas Monjalon wrote:
18/01/2018 05:12, Jeff Guo:
+ * It registers the callback for the specific device.
+ * Multiple callbacks cal be registered at the same time.
+ *
+ * @param device_name
+ * The device name, that is the param name of the struct rte_device,
Why not
18/01/2018 05:12, Jeff Guo:
> + * It registers the callback for the specific device.
> + * Multiple callbacks cal be registered at the same time.
> + *
> + * @param device_name
> + * The device name, that is the param name of the struct rte_device,
Why not using rte_device pointer?
> + * null v
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
5 matches
Mail list logo
