[Barrelfish-users] Question about Barrelfish server and client communication setup

[Robert Radkiewicz]

Hi,

so we found out it ourselves now.
For the record:
The information needed to setup a new channel can be exchanged with the 
messages in monitor.if and intermon.if.
In monitor.if the messages "bind_xxx_client_request" & 
"bind_xxx_service_request" hold the information sent from client to 
server and "bind_xxx_reply_monitor" & "bind_xxx_reply_client" hold the 
information in the reply back from server to client. These messages are 
the ones sent from the monitor to the local dispatcher.
The information sent from one monitor to another monitor are in 
intermon.if in the messages "bind_xxx_request" & "bind_xxx_reply".
This is also documented in the Barrelfish documentation TN-011, figure 4.1.

Robert


On 16.02.2013 20:39, Xiaowen Wang wrote:
> Hi, all,
>
> We are porting Barrelfish onto TilePro64 architecture. Now we plan to 
> use TilePro's UDN network to replace barrelfish's UMP to implement 
> inter-core communication. I notice that in Barrelfish's generic model, 
> the server first exports a service, and then the client binds that 
> service to initialize itself. And then the client will return 
> something to the server, and then the server initialize its part.
>
> As far as I know, the function ump_chan_bind() is to initialize the 
> client, and ump_chan_accept() is to initialize the server.
>
> My question is:
> is it possible to pass some values from client to server, and then the 
> server replies some values to the client, and which functions or 
> handlers is for this purpose?
>
>
> For our demultiplexing, we have different channels per core and need 
> to know to which channel_id  to send a message to. So we need to send 
> the client's channel_id to the server while binding and the server 
> needs to send back its channel_id to the client on the bind_reply.
>
>
> Best regards,
> Xiaowen
>
>
> _______________________________________________
> Barrelfish-users mailing list
> Barrelfish-users at lists.inf.ethz.ch
> https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20130217/4f47fcdf/attachment.html