DPDK patches and discussions
 help / color / mirror / Atom feed
From: "MICHAL KOLÁŘ" <MICH.K@seznam.cz>
To: <dev@dpdk.org>
Subject: Support for VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS / VHOST_USER_ADD_MEM_REG / VHOST_USER_REM_MEM_REG
Date: Fri, 15 Dec 2023 12:39:12 +0100 (CET)	[thread overview]
Message-ID: <3UX.yj{f.5}TcuT33D0m.1bV3hW@seznam.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]


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 vhost
-user message.




The solution would be to use the implemented VHOST_USER_PROTOCOL_F_CONFIGURE
_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

[-- Attachment #2: Type: text/html, Size: 869 bytes --]

                 reply	other threads:[~2023-12-15 11:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='3UX.yj{f.5}TcuT33D0m.1bV3hW@seznam.cz' \
    --to=mich.k@seznam.cz \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).