We will have a DAT Collaborative conference call this Friday Feb 3, 12:00-1:00pm EDT (9:00am-10:00am PDT). Moderator: Arkady Kanevsky Phone: 888-827-8686 ...
There is no DAT presentation at Data Centric Workshop at Sonoma this time. Instead we will have DAT BOF. I will participate remotely and James Lentini a DAPL...
Arkady, Your requirements are slightly different then the proposed set of requirements. "iii) DAPL Provider does not provide any identification that that the ...
Arlin, On Friday we agreed that receiver can not distinguish between 4 byte of Send or 4 bytes of Immediate data if RDMA Write with Immed is implemented as 2...
Arlin, It is too strong to state that Consumer should never send a message equal in size to the size of immediate data. Consumer knows from the context which...
If it is up to the ULP to separate out "normal" receive data from that associated with a write immediate, how is this different from the ULP doing a write...
... The data provided is to identify the completion notification that completes the RDMA Write to the data sink. So, yes, it is not really an "immediate"...
Roy, Can you explain, please? For IB the operation will be layered properly on Transport primitive. And on Recv side it will indicate in completion event DTO ...
There will be a DAPL BOF this evening from 19:30-20:00 in the Palm Tree Salon. I plan to setup a conference call for those of you who would like to participate...
I just want to get consensus on the requirements before we get too far. One thing I forgot is that with Infiniband, the receive with immediate provides the...
... If the application could be written transport independently, I would have no objection at all. Instead, it must be written in a transport-adaptive way and...
... The data sink knows whether the 4 bytes was sent as a message or as an immediate because it is clear in the ULP context. Possible methods: The expected...
I should stress that the only "additional" requirement I had added beyond the DAT meeting agreement is Provider attribute for the size of Immediate Data. It...
... Mine too.... ... primitive. ... I think you missed my larger point. The point was that the application must be written in such a way that it could...
I am not clear what you are proposing? A transport specific API? The current proposal provides on sending side: single post, and single completion in the error...
... Two points: First it is more like the_data = (DTO == 1) ? event->immediate : dto->buf; And further it is only on the receiving side. And only if the...
It is much simplier to handle immediate data as DAT extension. Spec changes are minimal. One extra field for DTO completion and for DAT_DTOS. One fix in...
But each of the multiple work requests follow the semantic of single completion per work request. It can be controlled by completion_flags but it still not a...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
