From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 45B47436FD; Fri, 15 Dec 2023 12:39:16 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F15DC40299; Fri, 15 Dec 2023 12:39:15 +0100 (CET) Received: from mxh.seznam.cz (mxh.seznam.cz [77.75.76.212]) by mails.dpdk.org (Postfix) with ESMTP id CF7AF4021F for ; Fri, 15 Dec 2023 12:39:14 +0100 (CET) Received: from email.seznam.cz by smtpc-mxh-5856c86478-72k8f (smtpc-mxh-5856c86478-72k8f [2a02:598:128:8a00::1000:69]) id 69d42a60e28e205369257b67; Fri, 15 Dec 2023 12:39:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seznam.cz; s=szn20221014; t=1702640354; bh=0IQCpZSUyRvZDSGCpaqsKxJa8eRgUJKJQnCj5zVLQgA=; h=Received:From:To:Subject:Date:Message-Id:Mime-Version:X-Mailer: Content-Type; b=fNy79YgR/TCBrpeTQOhD5CU+8oso3+xjB54nnfhxJfvSbcIDEBzhJ4hTb0cOesgAY qcuTTVv0m7GDlr68u4o4psM9e5uWwSMZo+CizE6pVOe6bgXfgX7G+PeNn3g9r7DQob Qzjh1/v+RLGtLf/NFe6tGsJKYP/e4db6FEEObrHaYMezbPRSOi3XGBPDKkCZDvyPCA t5BQS51Frx6r6Soe+2BHObh5HhJlIo7rpmtLKAv19lwD2eWrifazepw4jabAbMNBix LEJKUX0gcxIGTirYsIalULMh55sd4se0j2qlTd0ctJXac3cAlvftYhQtxU+idNQaiT ILOPFtunezkMg== Received: from unknown ([188.130.140.29]) by email.seznam.cz (szn-UNKNOWN-unknown) with HTTP; Fri, 15 Dec 2023 12:39:12 +0100 (CET) From: =?utf-8?q?MICHAL_KOL=C3=81=C5=98?= To: Subject: =?utf-8?q?Support_for_VHOST=5FUSER=5FPROTOCOL=5FF=5FCONFIGURE=5FM?= =?utf-8?q?EM=5FSLOTS_/_VHOST=5FUSER=5FADD=5FMEM=5FREG_/_VHOST=5FUSER=5FRE?= =?utf-8?q?M=5FMEM=5FREG?= Date: Fri, 15 Dec 2023 12:39:12 +0100 (CET) Message-Id: <3UX.yj{f.5}TcuT33D0m.1bV3hW@seznam.cz> Mime-Version: 1.0 (szn-mime-2.1.33) X-Mailer: szn-UNKNOWN-unknown Content-Type: multipart/alternative; boundary="=_471997dd7726322b200008ea=39e7dc40-2eb4-59ad-99d1-c714cbbc99c4_=" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --=_471997dd7726322b200008ea=39e7dc40-2eb4-59ad-99d1-c714cbbc99c4_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, I am solving the implementation of qemu-kvm with dpdk through vhost-user += VPP. I have a problem with the fact that we have AMD epic servers with 4 = numa nodes deployed in production. So 8 numa nodes for the entire server.= If we start virtualization and allow the guest to allocate all number of = nodes. This means the entire server (8 numa nodes) - thanks to gigabyte_= alignment, 9 memory regions will be created that will not fit into the vho= st -user message. The solution would be to use the implemented VHOST_USER_PROTOCOL_F_CONFIGU= RE _MEM_SLOTS with calls to VHOST_USER_ADD_MEM_REG and VHOST_USER_REM_MEM_REG= . Are you not considering implementing in DPDK? Thanks a lot. Kolar --=_471997dd7726322b200008ea=39e7dc40-2eb4-59ad-99d1-c714cbbc99c4_= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

I am solving the implemen= tation of qemu-kvm with dpdk through vhost-user + VPP. I have a problem wi= th the fact that we have AMD epic servers with 4 numa nodes deployed in pr= oduction. So 8 numa nodes for the entire server.

= If we start virtualization and allow the guest to allocate all number of n= odes. This means the entire server (8 numa nodes) - thanks to gigabyte_ali= gnment, 9 memory regions will be created that will not fit into the vhost-= user message.

The solution would be to use the im= plemented VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS with calls to VHOST_US= ER_ADD_MEM_REG and VHOST_USER_REM_MEM_REG.


Are you not considering implementing in DPDK?

Thanks a lot.
Kolar
--=_471997dd7726322b200008ea=39e7dc40-2eb4-59ad-99d1-c714cbbc99c4_=--