Changeset 36251 in project


Ignore:
Timestamp:
08/13/18 05:09:13 (8 days ago)
Author:
kon
Message:

reword

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/eggref/5/mailbox

    r36250 r36251  
    225225
    226226
     227== Bugs & Limitations
     228
     229* {{mailbox-wait!}}, {{mailbox-receive!}}, and {{mailbox-cursor-next}} must
     230not be used with a timeout value when the {{(current-thread)}} is the
     231{{##sys#primordial-thread}}!
     232
     233
    227234== Notes
    228235
    229 * Cannot wait with timeout on the primordial thread. So {{mailbox-wait!}},
    230 {{mailbox-receive!}}, and {{mailbox-cursor-next}} must not be used with a
    231 timeout value when the {{(current-thread)}} is the {{##sys#primordial-thread}}.
    232 
    233 * A '''deadlock''' is possible when using {{mailbox-wait!}},
    234 {{mailbox-receive!}}, or {{mailbox-cursor-next}}, should there be no other
    235 threads ''runnable''. When a mailbox is empty the {{(current-thread)}} is
    236 suspended (indefinite block). Then the scheduler looks for the next ready
     236* '{{mailbox-wait!}}, {{mailbox-receive!}}, and {{mailbox-cursor-next}}, are
     237susceptible to ''deadlock''. When a mailbox is empty the {{(current-thread)}}
     238is suspended (indefinite block). Then the scheduler looks for the next ready
    237239thread. If one is not available it signals ''deadlock''. Using a {{TIMEOUT}}
    238240will allow the calling thread to unblock eventually.
Note: See TracChangeset for help on using the changeset viewer.