Re: callout(9) and Giant lock

2009-07-13 Thread John Baldwin
On Sunday 28 June 2009 11:57:05 am Robert Watson wrote: On Sun, 28 Jun 2009, Sebastian Huber wrote: suppose that a certain time event triggered several callout functions. What happens if the first of these callout functions blocks on the Giant lock? Does this delay all further callout

Re: callout(9) and Giant lock

2009-07-13 Thread Robert N. M. Watson
On 13 Jul 2009, at 19:17, John Baldwin wrote: Callouts are marked as MPSAFE or non-MPSAFE when registered. If non-MPSAFE, we will acquire Giant automatically for the callout, but I believe we'll also try and sort non-MPSAFE callouts behind MPSAFE ones in execution order to minimize

Re: callout(9) and Giant lock

2009-07-13 Thread John Baldwin
On Monday 13 July 2009 2:49:24 pm Robert N. M. Watson wrote: On 13 Jul 2009, at 19:17, John Baldwin wrote: Callouts are marked as MPSAFE or non-MPSAFE when registered. If non-MPSAFE, we will acquire Giant automatically for the callout, but I believe we'll also try and sort

callout(9) and Giant lock

2009-06-28 Thread Sebastian Huber
Hi, suppose that a certain time event triggered several callout functions. What happens if the first of these callout functions blocks on the Giant lock? Does this delay all further callout functions until the Giant lock is available for the first callout function? What happens if one of the

Re: callout(9) and Giant lock

2009-06-28 Thread Robert Watson
On Sun, 28 Jun 2009, Sebastian Huber wrote: suppose that a certain time event triggered several callout functions. What happens if the first of these callout functions blocks on the Giant lock? Does this delay all further callout functions until the Giant lock is available for the first