>>> On 02.02.16 at 16:00, <yu.c.zh...@linux.intel.com> wrote: > The limit of 4G is to avoid the data missing from uint64 to uint32 > assignment. And I can accept the 8K limit for XenGT in practice. > After all, it is vGPU page tables we are trying to trap and emulate, > not normal page frames. > > And I guess the reason that one domain exhausting Xen's memory can > affect another domain is because rangeset uses Xen heap, instead of the > per-domain memory. So what about we use a 8K limit by now for XenGT, > and in the future, if a per-domain memory allocation solution for > rangeset is ready, we do need to limit the rangeset size. Does this > sounds more acceptable?
The lower the limit the better (but no matter how low the limit it won't make this a pretty thing). Anyway I'd still like to wait for what Ian may further say on this. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
