On 14-Nov-01 David Wolfskill wrote:
Built booted today's -CURRENT; saw the following on the console in
/var/log/messages:
Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
Nov 14 08:59:25 localhost /boot/kernel/kernel: 1st 0xc0427980 dev_pager
create @
:On 14-Nov-01 David Wolfskill wrote:
: Built booted today's -CURRENT; saw the following on the console in
: /var/log/messages:
:
: Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
: Nov 14 08:59:25 localhost /boot/kernel/kernel: 1st 0xc0427980 dev_pager
: create @
On 14-Nov-01 Matthew Dillon wrote:
:On 14-Nov-01 David Wolfskill wrote:
: Built booted today's -CURRENT; saw the following on the console in
: /var/log/messages:
:
: Nov 14 08:59:25 localhost /boot/kernel/kernel: lock order reversal
: Nov 14 08:59:25 localhost /boot/kernel/kernel: 1st
::This is due to the sx worker locks not using MTX_NOWITNESS with the pool
::mutex
::changes. It's not a problem though.
::
::--
::
::John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
:
: Would it make sense for me to add a new MTX flag that disables certain
:
Is there a good , current description of how why the various mutexe's
conditon variables are used for somewhere?? I see what they are doing
in the code, but would like to get the big picture of why they are used
in one place (and not another type)..
Thanks,
Glenn G.
I'm not
