Concurrent servicing of RPC requests?

Concurrent servicing of RPC requests?

Post by Robert Coo » Mon, 21 Mar 1994 20:47:21


I have a query regarding the ability of RPC servers to handle
multiple requests from clients concurrently. The CLIENT/SERVER
arrangement is as follows.

I have set up an RPC server which simply registers the procedure "myproc"
to be called when a request is received for the given procedure/version
combination and then calls svc_run() (which waits for RPC requests to arrive
and calls the appropriate service procedure). eg

        registerrpc(PROGNUM, VERSNUM, PROCNUM, myproc, xdr_void, xdr_u_long);
        /* Should never return. */

I have an RPC client which calls the remote "myproc" procedure via the above
RPC server as follows:

                xdr_void, 0, xdr_u_long, &result);

Once the server program is started on the remote host, running the client
program calls the procedure "myproc" on the remote machine and the result
is returned to the client as expected.

But if lots of client programs are calling the remote procedure "myproc"
simultaneously, these requests appear to be queued and processed serially one
after the other.

Is there a way of making svc_run() service the requests from the clients
concurrently instead of serially? i.e. I don't want a client to have to wait
for previous requests from other clients to be completed before its request
is executed.

Do I have to write my own asynchronous event handler to accomplish this?

Please E-mail any responses to me directly.

Thanks for any info,

 .-_|\   Robert Coote                        Phone : +61 7 365 4321
/     \  CiTR                                Fax   : +61 7 365 4399
\_.-._/  University of Queensland 4072      


1. RPC services without binding to RPC Bind/PortMap?

I have problem in creating (ONC/TI)RPC Servcer and Client which do not
require RPCBind/PortMapper (which I assume is possible)?

I have been succesful in being able to create a number of RPC services
using the top-level RPC calls.

I know that the lower level calls allow me to specify the transport
and such, and also allow me to not use RPCBind. But I seem to have
some difficulty doing so. I usually seem to get the server up and
running fine (or so it seems), but my client can never connect

Can anyone provide me with any sample code, hints, suggestion or
anything on how to go about doing crerating an RPC Server and Client
that does not use RPCBind/PortMapper.

2. statically-linked Pan binaries?

3. rpc.nfsd: cannot register service: rpc: timed out

4. tulip-driver vows

5. Concurrent Server with RPC

6. Linux + 3c619b Token Ring?

7. Multithreaded/Concurrent RPC

8. Changing modem connect speed

9. can rpc server be concurrent ??

10. socket concurrent server vs. RPC server

11. Sun's RPC and concurrent servers

12. Concurrent service clients number problem in Apache

13. Handling Multiple concurrent request from a single client