[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [v5][PATCH 10/16] tools: introduce some new parameters to set rdm policy
I'll update this next revision. And also rephrase this doc to address your comments below.FTR I think I indicated yesterday that I was satisfied with your explanation for why type=none exists as an option even at the xl level, namely that it allows us to change the default in the future. Campbell, Jackson had some different comments at this point, #1. Rename "type" to "strategy " and "none" to "ignore" --- a/tools/libxl/libxl_types.idl +++ b/tools/libxl/libxl_types.idl @@ -76,6 +76,17 @@ libxl_domain_type = Enumeration("domain_type", [ (2, "PV"), ], init_val = "LIBXL_DOMAIN_TYPE_INVALID") +libxl_rdm_reserve_strategy = Enumeration("rdm_reserve_strategy", [ + (0, "ignore"), + (1, "host"), + ]) + ... libxl_channel_connection = Enumeration("channel_connection", [ (0, "UNKNOWN"), (1, "PTY"), @@ -369,6 +380,11 @@ libxl_vnode_info = Struct("vnode_info", [ ("vcpus", libxl_bitmap), # vcpus in this node ]) +libxl_rdm_reserve = Struct("rdm_reserve", [ + ("strategy", libxl_rdm_reserve_strategy), + ("reserve", libxl_rdm_reserve_flag), + ]) + #2. Don't expose "ignore" to user and just keep "host" as the defaultHe told me he would discuss this with you, but sounds he didn't do this, or I'm missing something here? Thanks Tiejun _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |