Do you mean 'pull' or 'poll' on read, or 'push' on write? :-) In any case, Alan is right, and the lowest latency way for virtual machin es to share data is with a DCSS.
cheers, Jeff On Fri, 3 Apr 2009 16:47:58 -0500, Gary M. Dennis <gary.den...@mantissa.c om> wrote: >Something along these lines > >Guests pull on read >Servers pull on write >Async only > > >--. .- .-. -.-- > >Gary Dennis >Mantissa > >0 ... living between the zeroes ... 0 > >On 4/3/09 4:26 PM, "Alan Altmark" <alan_altm...@us.ibm.com> wrote: > >> On Friday, 04/03/2009 at 03:38 EDT, "Gary M. Dennis" >> <gary.den...@mantissa.com> wrote: >>> What I was trying to determine if there was a way to use ZFS on >> OpenSolaris >>> System z as a high speed space management vehicle while bypassing >> conventional >>> transport layers? For example, let?s say there existed a way to push >> data to >>> the IO appliance cross-memory (guest to ZFZ, ZFS to guest) such that an >> >>> interface in the appliance could act as a local proxy for each guest >> using the >>> service. >> >> Just in case you are trying to connect Diag 0x248 with "push data" to >> OpenSolaris, don't bother. First, Diag 0x248 is a read-only function. >> Second, OpenSolaris, like Linux, is DAT ON. That means they cannot cr eate >> or access Data Spaces. Your only shared-memory solution is a DCSS. >> >> Alan Altmark >> z/VM Development >> IBM Endicott >> >======================== ========================= ========================
