Re: [dpdk-dev] [RFC 0/5] Use correct memory ordering in eal functions

2021-03-02 Thread Honnappa Nagarahalli
> > > rte_eal_remote_launch and rte_eal_wait_lcore need to provide correct > > memory ordering to address the data communication from main core to > > worker core and vice versa. > > > > There are 2 use cases: > > 1) All the store operations (meant for worker) by main core should be > > visible

Re: [dpdk-dev] [RFC 0/5] Use correct memory ordering in eal functions

2021-03-01 Thread Stephen Hemminger
On Wed, 24 Feb 2021 15:20:13 -0600 Honnappa Nagarahalli wrote: > rte_eal_remote_launch and rte_eal_wait_lcore need to provide > correct memory ordering to address the data communication from > main core to worker core and vice versa. > > There are 2 use cases: > 1) All the store operations (mean

[dpdk-dev] [RFC 0/5] Use correct memory ordering in eal functions

2021-02-24 Thread Honnappa Nagarahalli
rte_eal_remote_launch and rte_eal_wait_lcore need to provide correct memory ordering to address the data communication from main core to worker core and vice versa. There are 2 use cases: 1) All the store operations (meant for worker) by main core should be visible to worker core before the worker