Le mardi 05 septembre 2023 à 17:16 +0200, Thomas Lamprecht a écrit : > Am 05/09/2023 um 17:10 schrieb DERUMIER, Alexandre: > > > > > > The advantage with 'max' is that it can be used for both, hotplug > > > with > > > dimms and virtio-mem. Otherwise, we'd need two different sub- > > > options > > > depending on hotplug method. > > > > > yes, that's what I thinked too, it could be great to have same api > > call > > with same options, with or without virtio-mem. > > > > (virtio-mem will be the default for new linux distro, but for > > windows > > or older linux distro, we still need to use old dimm method) > > > > > > > > My first idea for the gui, for the max value, was a combobox > > displaying > > an hint with mem topology, something like: > > > > max = 64GB : 64 x 1GB dimm > > max = 128GB: 64 x 2GB dimm > > ... > > > > (or maybe it could be a hint outside a simple integer field) > > > > We could still allow setting the DIMM size in the UI with a simple > integer > field and a step size of 1 (GB) and then calculate the max from that? > > yes, it could work too. Maybe a dimm size field, changing the max value , and at the same time, changing the max value is changing the dimm size field ?
and for virtio-mem, dimmsize can be replace by chunk size _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
