[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 3 of 4 RFC] xl/remus: Control network buffering in remus callbacks
Ian Campbell writes ("Re: [PATCH 3 of 4 RFC] xl/remus: Control network buffering in remus callbacks"): > This really needs Ian's review WRT the lifetime of the remus context > object vs. the ao machinery. IOW I'm not sure if this is the appropriate > gc to be using or if one associated with the ao context isn't required. AFAICT the remus_ctx is allocated from the ao's gc because of this: > > void libxl__domain_suspend(libxl__egc *egc, libxl__domain_suspend_state > > *dss) ... STATE_AO_GC(dss->ao); ... > > + dss->remus_ctx = setup_remus_ctx(gc, r_info); So "gc" in libxl__domain_suspend is the ao gc, and that ends up being used for everything. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |