A bit verbose. I shortened it to A new feature, VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS, has been added to the vhost-user protocol. VMs with vhost-user device backends which support this feature will not be subject to the current max RAM slots limit of 8 and will be able to hot-add memory as many times as the target platform supports.
Peter, can you pls allow Raphael wiki access? I don't remember how it's done ... On Wed, Jul 29, 2020 at 09:17:27PM -0600, Raphael Norwitz wrote: > How about something like: > "A new feature, VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS, has been > added to the vhost-user protocol which, when negotiated, changes the > way QEMU transmit memory regions to backend devices. Instead of > sending all regions in a single VHOST_USER_SET_MEM_TABLE message, QEMU > will send supporting backends individual VHOST_USER_ADD_MEM_REG and > VHOST_USER_REM_MEM_REG messages to update the devices memory tables. > VMs with vhost-user device backends which support this feature will > not be subject to the max RAM slots limit of 8 and will be able to > hot-add memory as many times as the target platform supports. Backends > which do not support VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS are > unaffected." > > I don't have permission to edit the wiki. How can I get permission? Or > can someone post it for me? > > On Wed, Jul 29, 2020 at 8:19 AM Michael S. Tsirkin <m...@redhat.com> wrote: > > > > On Tue, Jul 28, 2020 at 09:16:10PM -0600, Raphael Norwitz wrote: > > > Hi mst, > > > > > > Looking at the current changelog > > > https://wiki.qemu.org/ChangeLog/5.1#virtio, I don't see any mention of > > > the VHOST_USER_PROTOCOL_F_CONFIG_MEM_SLOTS protocol feature. It is a > > > user visible change so shouldn't we add a note? > > > > > > Thanks, > > > Raphael > > > > I didn't look at updating the changelog yet. > > Would be great if you could write up new vhost user things. > > > > -- > > MST > >