[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [v10][PATCH 11/16] tools/libxl: detect and avoid conflicts with RDM

Chen, Tiejun writes ("Re: [v10][PATCH 11/16] tools/libxl: detect and avoid 
conflicts with RDM"):
> [Ian Jackson:]
> > The most obvious answer to me would be that if an rdms array is
> > specified, the strategy should be ignored.  That is how the automatic
> > numa placement API works.
> I'm not familiar with this.
> Do you mean this?
>      if (d_config->num_rdms)
> But except this global strategy, we also have per-device setting so 
> maybe something like this?
>      if (d_config->num_rdms)
>          return 0;

This latter was the kind of approach I had in mind.  I think that will
do for 4.6.

> > But another answer would be to take the union of the specified
> > regions.  That would be more complicated, because the union would have
> > to be computed.
> >
> >>               if (d_config->rdms[i].start == rdm_start)
> >>                   return;
> >
> > That doesn't, of course, compute the union.
> Sorry I don't understand what the "take the union of the specified 
> regions" is here.

A "region" is a subset of the address space.  I meant the set union:

That is, an address would be reserved if it was reserved in any of the
rdm regions implied by the config.

The explicitly specified regions might overlap with the computed ones,
without being identical. Computing the union would not be entirely


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.