Displaying 4 results from an estimated 4 matches for "alignsize".
Did you mean:
align_size
2020 Jun 16
4
NVDIMM sizes and DIMM hot plug
...clarify, how libvirt makes the DIMM address above. How is
the NVDIMM memory range determined? According to my experiments, it
seems the NVDIMM specified <size> is taken, NVDIMM <label> size is
subtracted from it and the resulting value is reduced to the nearest
multiple of NVDIMM <alignsize>. Is this observation correct? Is it
guaranteed to be stable in future versions? I need to determine the
right NVDIMM size to make the subsequent memory modules correctly
aligned and then I can't change the NVDIMM size, to not damage data
stored in the NVDIMM.
Additionally, when adjustin...
2020 Jun 18
1
Re: NVDIMM sizes and DIMM hot plug
...'t risk data loss.
>> the NVDIMM memory range determined? According to my experiments, it
>> seems the NVDIMM specified <size> is taken, NVDIMM <label> size is
>> subtracted from it and the resulting value is reduced to the nearest
>> multiple of NVDIMM <alignsize>. Is this observation correct? Is it
>> guaranteed to be stable in future versions? I need to determine the
>> right NVDIMM size to make the subsequent memory modules correctly
>> aligned and then I can't change the NVDIMM size, to not damage data
>> stored in the...
2020 Jun 16
0
Re: NVDIMM sizes and DIMM hot plug
...t makes the DIMM address above. How is
> the NVDIMM memory range determined? According to my experiments, it
> seems the NVDIMM specified <size> is taken, NVDIMM <label> size is
> subtracted from it and the resulting value is reduced to the nearest
> multiple of NVDIMM <alignsize>. Is this observation correct? Is it
> guaranteed to be stable in future versions? I need to determine the
> right NVDIMM size to make the subsequent memory modules correctly
> aligned and then I can't change the NVDIMM size, to not damage data
> stored in the NVDIMM.
Libvirt...
2020 Jun 16
0
Re: NVDIMM sizes and DIMM hot plug
...qemuDomainUpdateMemoryDeviceInfo'.
> the NVDIMM memory range determined? According to my experiments, it
> seems the NVDIMM specified <size> is taken, NVDIMM <label> size is
> subtracted from it and the resulting value is reduced to the nearest
> multiple of NVDIMM <alignsize>. Is this observation correct? Is it
> guaranteed to be stable in future versions? I need to determine the
> right NVDIMM size to make the subsequent memory modules correctly
> aligned and then I can't change the NVDIMM size, to not damage data
> stored in the NVDIMM.
Unfort...