[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] RE: Co-scheduling HVM domains...



On Tuesday 27 March 2007, Roger Cruz wrote:
> 2) We'll have a lot more domain pairs than CPUs. They (the pairs) run
> independent applications of each other so batching requests is not a
> choice at this point.  But we do know that the two pairs will
> communicate (server-client app) and will use a shared memory construct
> to pass the messages back (no IP connection, just a proprietary comm.
> protocol using shared memory). There are latency issues involved in
> getting to those packets so if we could guarantee that when the client
> makes a request, the server will get it (almost) immediately, then we're
> golden.  So, I'm interested in tweaking the scheduling algorithm to
> guarantee that the server can get on the CPU after the client runs.

have you managed to get that shared memory working on Xen?  i guess that would 
be your first problem, CPU scheduling a very distant second.


-- 
Javier

Attachment: pgp9FiYKTEk1e.pgp
Description: PGP signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.