Searched hist:197643 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-10.3-release/sys/sys/ | ||
| H A D | rwlock.h | diff 197643 Wed Sep 30 13:32:19 MDT 2009 attilio When releasing a read/shared lock we need to use a write memory barrier in order to avoid, on architectures which doesn't have strong ordered writes, CPU instructions reordering. Diagnosed by: fabio Reviewed by: jhb Tested by: Giovanni Trematerra <giovanni dot trematerra at gmail dot com> |
| H A D | sx.h | diff 197643 Wed Sep 30 13:32:19 MDT 2009 attilio When releasing a read/shared lock we need to use a write memory barrier in order to avoid, on architectures which doesn't have strong ordered writes, CPU instructions reordering. Diagnosed by: fabio Reviewed by: jhb Tested by: Giovanni Trematerra <giovanni dot trematerra at gmail dot com> |
| /freebsd-10.3-release/sys/kern/ | ||
| H A D | kern_rwlock.c | diff 197643 Wed Sep 30 13:32:19 MDT 2009 attilio When releasing a read/shared lock we need to use a write memory barrier in order to avoid, on architectures which doesn't have strong ordered writes, CPU instructions reordering. Diagnosed by: fabio Reviewed by: jhb Tested by: Giovanni Trematerra <giovanni dot trematerra at gmail dot com> |
| H A D | kern_sx.c | diff 197643 Wed Sep 30 13:32:19 MDT 2009 attilio When releasing a read/shared lock we need to use a write memory barrier in order to avoid, on architectures which doesn't have strong ordered writes, CPU instructions reordering. Diagnosed by: fabio Reviewed by: jhb Tested by: Giovanni Trematerra <giovanni dot trematerra at gmail dot com> |
Completed in 177 milliseconds