On 25/01/2017 11:56, Thomas Monjalon wrote:
[..]
It does not describe exactly the use-case it is fixing (same in commit message).
I guess you saw an issue when creating a vdev in the primary process and
another one in a secondary process, erasing the data of the first one.
In my use-case the secondary process is proc_info, which appeared to be
blanking the shared memory then leaving the NULL-pointer landmines for
the primary process to land on. I'm not entirely sure why this type of
secondary process needs to be running any ethdev startup code at all, as
all it is doing is pulling data out of shared memory..
My previous proposal was:
memset(eth_dev->data, 0, sizeof(*eth_dev->data))
It is better to avoid reference to the global array rte_eth_dev_data.
Git rebase screwed up, and it got lost en-route :(
..Remy
