Hello all, is there a way (network exepted) to make a xenU and xen0 communicate. I''m thinking at something like a ipc or a pipe without having to open a socket on one side and to listen to the socket on the other. Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> is there a way (network exepted) to make a xenU and xen0 communicate. > I''m thinking at something like a ipc or a pipe without having to open a > socket on one side and to listen to the socket on the other. > RegardsThere''s the control message channel (soon to be replaced by xenstore / xenbus) but these aren''t meant for high bandwidth comms. I''ll be looking at user-level interdomain shared memory soon, if that''s any help to you. Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, the user level interdomain memory will be accessible throw a virual device or just by programming ? If it is the first case i''m interested, otherwise i''ll do programming with socket thus avoiding development from you. Regards Matthieu On August 2, 3:46 pm Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > is there a way (network exepted) to make a xenU and xen0 communicate. > > I''m thinking at something like a ipc or a pipe without having to open > > a socket on one side and to listen to the socket on the other. > > Regards > > There''s the control message channel (soon to be replaced by xenstore / > xenbus) but these aren''t meant for high bandwidth comms. > > I''ll be looking at user-level interdomain shared memory soon, if that''s > any help to you. > > Cheers, > Mark >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> the user level interdomain memory will be accessible throw a virual device > or just by programming ?I''ll be supporting it via XenFS, so the applications in different domains will just mmap the same file in a XenFS share and it''ll Just Work(TM).> If it is the first case i''m interested, otherwise i''ll do programming with > socket thus avoiding development from you.It''ll be a while before you see XenFS in a release - writing a full filesystem is going to be a pretty time consuming task. You should probably write to the sockets API if you have an immediate requirement to get this working. Later on you can convert to my shared memory / Xen-aware networking stuff if you need the performance. Cheers, Mark> Regards > Matthieu > > On August 2, 3:46 pm Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote: > > > is there a way (network exepted) to make a xenU and xen0 communicate. > > > I''m thinking at something like a ipc or a pipe without having to open > > > a socket on one side and to listen to the socket on the other. > > > Regards > > > > There''s the control message channel (soon to be replaced by xenstore / > > xenbus) but these aren''t meant for high bandwidth comms. > > > > I''ll be looking at user-level interdomain shared memory soon, if that''s > > any help to you. > > > > Cheers, > > Mark > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On August 4, 4:40 pm Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > the user level interdomain memory will be accessible throw a virual > > device or just by programming ? > > I''ll be supporting it via XenFS, so the applications in different > domains will just mmap the same file in a XenFS share and it''ll Just > Work(TM).In deed, looks promising. If i have well understood it''s a filesystem which only reside in memory and memory block can be mmaped by different domains.> > If it is the first case i''m interested, otherwise i''ll do programming > > with socket thus avoiding development from you. > > It''ll be a while before you see XenFS in a release - writing a full > filesystem is going to be a pretty time consuming task. You should > probably write to the sockets API if you have an immediate requirement > to get this working. Later on you can convert to my shared memory / > Xen-aware networking stuff if you need the performance. > > Cheers, > Mark > > > Regards > > Matthieu > > > > On August 2, 3:46 pm Mark Williamson <mark.williamson@cl.cam.ac.uk> > > > > wrote: is there a way (network exepted) to make a xenU and xen0 > > > > communicate. I''m thinking at something like a ipc or a pipe > > > > without having to open a socket on one side and to listen to the > > > > socket on the other. Regards > > > > > > There''s the control message channel (soon to be replaced by > > > xenstore / xenbus) but these aren''t meant for high bandwidth comms. > > > > > > I''ll be looking at user-level interdomain shared memory soon, if > > > that''s any help to you. > > > > > > Cheers, > > > Mark > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I''ll be supporting it via XenFS, so the applications in different > > domains will just mmap the same file in a XenFS share and it''ll Just > > Work(TM). > > In deed, looks promising. > If i have well understood it''s a filesystem which only reside in memory and > memory block can be mmaped by different domains.Yep. It''ll also enable high performance filesystem sharing using an interdomain buffer cache and finally a filesystem level copy-on-write mechanism. Basically, loads of nice stuff. It''ll also prevent global warming, acid rain and stop gerbils falling over :-) Cheers, Mark> > > If it is the first case i''m interested, otherwise i''ll do programming > > > with socket thus avoiding development from you. > > > > It''ll be a while before you see XenFS in a release - writing a full > > filesystem is going to be a pretty time consuming task. You should > > probably write to the sockets API if you have an immediate requirement > > to get this working. Later on you can convert to my shared memory / > > Xen-aware networking stuff if you need the performance. > > > > Cheers, > > Mark > > > > > Regards > > > Matthieu > > > > > > On August 2, 3:46 pm Mark Williamson <mark.williamson@cl.cam.ac.uk> > > > > > > > > wrote: is there a way (network exepted) to make a xenU and xen0 > > > > > communicate. I''m thinking at something like a ipc or a pipe > > > > > without having to open a socket on one side and to listen to the > > > > > socket on the other. Regards > > > > > > > > There''s the control message channel (soon to be replaced by > > > > xenstore / xenbus) but these aren''t meant for high bandwidth comms. > > > > > > > > I''ll be looking at user-level interdomain shared memory soon, if > > > > that''s any help to you. > > > > > > > > Cheers, > > > > Mark > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users