[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v9 1/9] xen: vnuma topology and subop hypercalls
>>> On 05.09.14 at 05:27, <ufimtseva@xxxxxxxxx> wrote: > On Wed, Sep 3, 2014 at 4:28 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote: >>>>> On 03.09.14 at 02:46, <ufimtseva@xxxxxxxxx> wrote: >>> That is true. But taking into account that there are no buses support >>> yet added, absence of memory and buses for a vNUMA node >>> seem to be useless. And vNUMA can mimic hardware NUMA as close as >>> possible, but I think the degree of this is pretty much our choice. >>> With further extension of vNUMA to include buses I think this check >>> will naturally disappear. >> >> I have to admit that I struggle with the references to "buses" in your >> reply. Could you perhaps give some context (not the least because >> already known future extensions may call for making provisions for >> them in the public interface)? > > Sorry Jan, looks like I have missed that one. > > I meant NUMA I/O when was referring to buses. > For example from here/ > http://en.community.dell.com/cfs-file.ashx/__key/telligent-evolution-compone > nts-attachments/13-4491-00-00-20-26-69-46/NUMA-for-Dell-PowerEdge-12G-Servers > .pdf > > Or here NUMA I/O = PCIe : > http://events.linuxfoundation.org/sites/events/files/eeus13_shelton.pdf > > In earlier discussions of vNUMA, numa I/O was mentioned but never > really looked at yet from implementation point of view. Ah, that clarifies matters. Yes, we'll certainly want to do something in that direction, but I don't currently see this needing extension of the proposed hypercalls. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |