> Will your Xen guest memory sharing approach create OS portability
> headaches?
Yes, probably ;-)
Seriously, though, filesystem drivers are *extremely* OS-dependent. XenFS
probably even more so since it''s very intimately tied to the memory
management routines. Some of it will be portable (I''m splitting these
bits
out), but there''ll always need to be a large proportion of OS-dependent
filesystem goop. It''ll certainly be a while before it works with
anything
other than Linux.
The other issue is that *fully* supporting XenFS will require source code
access. Windows would either need to use a dumb XenFS client, *or* have some
outside assistance (Michael Vrable and I have been talking about similar
techniques, though for slightly different reasons).
> It would obviously be desirable to maintain one general
> scheme that works in *nix, Windows, etc. Windows processes can map
> files with MapViewOfFile(), but my understanding is that creating a
> Windows file system is difficult.
It wouldn''t surprise me! My understanding is that Linux is one of the
nicer
OSes to write a filesystem for, although that information may be out of date
(and it''s faaaaaaar from straightforward).
> Sending IOCTL''s to exotic character devices is boring and not half
as
> elegant, but isn''t it the most portable approach?
The filesystem-based mmap trick basically comes "for free" as a result
of my
implementation. If you really want the semantics of file-backed memory it
may make more sense; if you just want plain shared memory the special device
you propose would be better.
We should do both :-)
Cheers,
Mark
> -steve
>
> -----Original Message-----
> From: Mark Williamson [mailto:mark.williamson@cl.cam.ac.uk]
> Sent: Thursday, November 03, 2005 3:22 PM
> To: xen-devel@lists.xensource.com
> Cc: Christopher Clark; King, Steven R; NAHieu
> Subject: Re: [Xen-devel] Question on xc_gnttab_map_grant_ref()
>
> To expand:
>
> I''m working towards a shared-memory NFS-style filesystem for Xen
guests.
> This will allow high-performance data sharing within one host. This
> leverages direct memory sharing to maximise performance and make better
> use of the available RAM.
>
> A bonus feature of this direct sharing approach is that applications
> running in different domains on the same host should be able to share
> memory by both using a simple mmap() call. This avoids us having to
> introduce any new wacky semantics / exotic character devices; sharing
> should work similarly to the case of two applications in one domain.
>
> Cheers,
> Mark
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel