Changes between Version 2 and Version 3 of Ticket #11497, comment 12


Ignore:
Timestamp:
Dec 13, 2014, 4:04:28 PM (9 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11497, comment 12

    v2 v3  
    1 IIRC think ports are created with a certain capacity, and start *dropping* new incomings if write_port incomings come fast enough to override that capacity before read_port removes them (my experience on ports is almost only with BLoopers: their port is [http://grok.bikemonkey.org/source/xref/haiku/src/kits/app/Looper.cpp#963 created] with something like [http://grok.bikemonkey.org/source/xref/haiku/headers/build/os/app/Looper.h#13 200]  slots, and the thread tries to run as fast as possible to move them safely to a BMessageList where capacity is not limited... yet I know from trying unreasonable stuff with them that even that can be overwhelmed, I could e.g. send 201+ BMessages before the thread would wake up or be available).
     1IIRC think ports are created with a certain capacity, and start <strike>dropping</strike> new incomings if write_port incomings come fast enough to override that capacity before read_port removes them (my experience on ports is almost only with BLoopers: their port is [http://grok.bikemonkey.org/source/xref/haiku/src/kits/app/Looper.cpp#963 created] with something like [http://grok.bikemonkey.org/source/xref/haiku/headers/build/os/app/Looper.h#13 200]  slots, and the thread tries to run as fast as possible to move them safely to a BMessageList where capacity is not limited... yet I know from trying unreasonable stuff with them that even that can be overwhelmed, I could e.g. send 201+ BMessages before the thread would wake up or be available).
    22
    33==