On Thu, Mar 17, 2016 at 04:29:32PM +0100, Thomas Monjalon wrote:
> 2016-02-24 14:47, Ilya Maximets:
> > Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer
> > algorithm and contains almost all to be thread-safe, but it's not.
> >
> > This set adds required changes.
> >
> > First patch in set is a standalone patch that fixes many times discussed
> > issue with barriers on different architectures.
> >
> > Second and third adds fixes to make rte_vhost_enqueue_burst thread safe.
>
> My understanding is that we do not want to pollute Rx/Tx with locks.
>
> Huawei, Yuanhan, Bruce, do you confirm?
Huawei would like to do that, and I'm behind that. Let's do it. The
question is can we do that in this release? As I replied in another
thread, I'm wondering we might need do an announce first and do it
in next release?
Both are Okay to me; I just want to know which one is more proper.
Thoughts?
--yliu
