Change buffer invalidataion FMQ to unsync

Buffer Invalidation FMQ is designed as a shared FMQ between clients in
order to minimize memory consumption. In that case, regarding FMQ is
unsync FMQ in order to not to block writer in any situation.

Bug: 112203066
Change-Id: I58989ccd332ba790193007f43dd66ecbd617f484
This commit is contained in:
Sungtak Lee
2018-09-14 14:57:02 -07:00
parent 51a04b2fe2
commit 5c8e455d73
2 changed files with 2 additions and 2 deletions

View File

@@ -68,5 +68,5 @@ interface IAccessor {
generates (ResultStatus status, IConnection connection,
int64_t connectionId,
fmq_sync<BufferStatusMessage> toFmqDesc,
fmq_sync<BufferInvalidationMessage> fromFmqDesc);
fmq_unsync<BufferInvalidationMessage> fromFmqDesc);
};

View File

@@ -100,7 +100,7 @@ struct BufferStatusMessage {
struct BufferInvalidationMessage {
/**
* Buffers from fromBufferId to toBufferId must be invalidated.
* Both of fromBufferId and toBufferId are inclusive.
* fromBufferId is inclusive, but toBufferId is not inclusive.
* If fromBufferId > toBufferID, wrap happens. In that case
* the wrap is based on UINT32_MAX.
*/