Displaying 2 results from an estimated 2 matches for "d57ed95".
2011 Nov 29
4
[RFC] virtio: use mandatory barriers for remote processor vdevs
...g systems on two (separate) processors, each of
which might either be UP or SMP.
To control the ordering of memory references when the vrings are shared
between two external processors, we must always use mandatory barriers.
A trivial, albeit sub-optimal, solution would be to simply revert
commit d57ed95 "virtio: use smp_XX barriers on SMP". Obviously, though,
that's going to have a negative impact on performance of SMP-based
virtualization use cases.
A different approach, as demonstrated by this patch, would pick the type
of memory barriers, in run time, according to the requirement...
2011 Nov 29
4
[RFC] virtio: use mandatory barriers for remote processor vdevs
...g systems on two (separate) processors, each of
which might either be UP or SMP.
To control the ordering of memory references when the vrings are shared
between two external processors, we must always use mandatory barriers.
A trivial, albeit sub-optimal, solution would be to simply revert
commit d57ed95 "virtio: use smp_XX barriers on SMP". Obviously, though,
that's going to have a negative impact on performance of SMP-based
virtualization use cases.
A different approach, as demonstrated by this patch, would pick the type
of memory barriers, in run time, according to the requirement...