Re: [dpdk-dev] Reader-Writer lock starvation issues

2021-01-11 Thread Honnappa Nagarahalli
> > > >> > >> The current version of rte_rwlock doesn't do what it says in the > >> documentation. > >> " The lock is used to protect data that allows multiple readers in > >> parallel, but only one writer. All readers are blocked until the writer is > finished writing." > >> > >> The problem i

Re: [dpdk-dev] Reader-Writer lock starvation issues

2021-01-11 Thread Ferruh Yigit
On 1/8/2021 9:27 PM, Honnappa Nagarahalli wrote: The current version of rte_rwlock doesn't do what it says in the documentation. " The lock is used to protect data that allows multiple readers in parallel, but only one writer. All readers are blocked until the writer is finished writing."

Re: [dpdk-dev] Reader-Writer lock starvation issues

2021-01-08 Thread Honnappa Nagarahalli
> > The current version of rte_rwlock doesn't do what it says in the > documentation. > " The lock is used to protect data that allows multiple readers in parallel, > but > only one writer. All readers are blocked until the writer is finished > writing." > > The problem is that the current

[dpdk-dev] Reader-Writer lock starvation issues

2021-01-08 Thread Stephen Hemminger
The current version of rte_rwlock doesn't do what it says in the documentation. " The lock is used to protect data that allows multiple readers in parallel, but only one writer. All readers are blocked until the writer is finished writing." The problem is that the current implementation does not