Transport Sample Protocol - Tasks: task #4737, Implement zero copy and reversed...
You are not allowed to post comments on this tracker with your current authentication level.
task #4737: Implement zero copy and reversed blackboard
Submitter: | Eric NOULARD <erk> | ||
Submitted: | Tue 04 Oct 2005 08:19:37 AM UTC | ||
Category: | Blackboard | Should Start On: | Mon 03 Oct 2005 10:00:00 PM UTC |
Should be Finished on: | Mon 03 Oct 2005 10:00:00 PM UTC | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
The bb_provider use its own shadow blackboard
for distribution which makes memory consumption fairly
high with huge blackboard.
We may implements 2 things in order to cope with this:
1) A zero copy mode for the bb_provider which
should work directly with the "shared blackboard"
without shadow copy.
This could be -z command line option
2) Re-Enable a 'synchronized' mode where the bb_provider should
signal the BB user (using the message queue with
bb_simple_synchro_go(BB_SIMPLE_MSGID_SYNCHRO_COPY_ACK)
that the data has effectively
been copied (or distributed if in zero copy mode)
(this mode should be failry easy to implements
since code is there but commented)
This could be a -s command line option.
3) A good companion to zero copy BB would be
a reversed blackboard were someone bb_publishing
will pass an address of local var as a supplementary
argument.
The reversed BB would memorize the @ and the
BB user may bb_reverse_synchronize wich will
automatically copy value from local address
provided during publish to shared published data.
This 'reversed' blackboard would ease TSP distribution
for application who have to stick with local var
instead of shared memory BB model with pointer.
Using a bb_provider in zero copy mode will provide
low cost TSP distribution.
(seek for "reversed blacboard" in tsp-devel)