diff for duplicates of <20200727193326.03525888@redhat.com> diff --git a/a/1.txt b/N1/1.txt index 7152741..bfa9d59 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -322,3 +322,88 @@ in guest OS). > Any information on why the config latency and bandwidth values are not > applied, would be appreciated. > + +-- +You received this bug notification because you are a member of qemu- +devel-ml, which is subscribed to QEMU. +https://bugs.launchpad.net/bugs/1888923 + +Title: + Configured Memory access latency and bandwidth not taking effect + +Status in QEMU: + New + +Bug description: + I was trying to configure latencies and bandwidths between nodes in a + NUMA emulation using QEMU 5.0.0. + + Host : Ubuntu 20.04 64 bit + Guest : Ubuntu 18.04 64 bit + + The machine configured has 2 nodes. Each node has 2 CPUs and has been + allocated 3GB of memory. The memory access latencies and bandwidths + for a local access (i.e from initiator 0 to target 0, and from + initiator 1 to target 1) are set as 40ns and 10GB/s respectively. The + memory access latencies and bandwidths for a remote access (i.e from + initiator 1 to target 0, and from initiator 0 to target 1) are set as + 80ns and 5GB/s respectively. + + The command line launch is as follows. + + sudo x86_64-softmmu/qemu-system-x86_64 \ + -machine hmat=on \ + -boot c \ + -enable-kvm \ + -m 6G,slots=2,maxmem=7G \ + -object memory-backend-ram,size=3G,id=m0 \ + -object memory-backend-ram,size=3G,id=m1 \ + -numa node,nodeid=0,memdev=m0 \ + -numa node,nodeid=1,memdev=m1 \ + -smp 4,sockets=4,maxcpus=4 \ + -numa cpu,node-id=0,socket-id=0 \ + -numa cpu,node-id=0,socket-id=1 \ + -numa cpu,node-id=1,socket-id=2 \ + -numa cpu,node-id=1,socket-id=3 \ + -numa dist,src=0,dst=1,val=20 \ + -net nic \ + -net user \ + -hda testing.img \ + -numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-latency,latency=40 \ + -numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-bandwidth,bandwidth=10G \ + -numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-latency,latency=80 \ + -numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-bandwidth,bandwidth=5G \ + -numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-latency,latency=80 \ + -numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-bandwidth,bandwidth=5G \ + -numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-latency,latency=40 \ + -numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-bandwidth,bandwidth=10G \ + + Then the latencies and bandwidths between the nodes were tested using + the Intel Memory Latency Checker v3.9 + (https://software.intel.com/content/www/us/en/develop/articles/intelr- + memory-latency-checker.html). But the obtained results did not match + the configuration. The following are the results obtained. + + Latency_matrix with idle latencies (in ns) + + Numa Node + . .0. . .1. + 0 36.2 36.4 + 1 34.9 35.4 + + Bandwidth_matrix with memory bandwidths (in MB/s) + + Numa Node + . . .0. . . .1. + 0 15167.1 15308.9 + 1 15226.0 15234.0 + + A test was also conducted with the tool “lat_mem_rd” from lmbench to + measure the memory read latencies. This also gave results which did + not match the config. + + Any information on why the config latency and bandwidth values are not + applied, would be appreciated. + +To manage notifications about this bug go to: +https://bugs.launchpad.net/qemu/+bug/1888923/+subscriptions diff --git a/a/content_digest b/N1/content_digest index dd6ffdb..c2d4d98 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,8 @@ "ref\0159566199879.4877.1642879405857907906.malonedeb@wampee.canonical.com\0" - "From\0Igor Mammedov <imammedo@redhat.com>\0" + "From\0Igor <1888923@bugs.launchpad.net>\0" "Subject\0Re: [Bug 1888923] [NEW] Configured Memory access latency and bandwidth not taking effect\0" - "Date\0Mon, 27 Jul 2020 19:33:26 +0200\0" - "To\0Vishnu Dixit <1888923@bugs.launchpad.net>\0" - "Cc\0qemu-devel@nongnu.org\0" + "Date\0Mon, 27 Jul 2020 17:33:26 -0000\0" + "To\0qemu-devel@nongnu.org\0" "\00:1\0" "b\0" "On Sat, 25 Jul 2020 07:26:38 -0000\n" @@ -329,6 +328,91 @@ "> \n" "> Any information on why the config latency and bandwidth values are not\n" "> applied, would be appreciated.\n" - > + ">\n" + "\n" + "-- \n" + "You received this bug notification because you are a member of qemu-\n" + "devel-ml, which is subscribed to QEMU.\n" + "https://bugs.launchpad.net/bugs/1888923\n" + "\n" + "Title:\n" + " Configured Memory access latency and bandwidth not taking effect\n" + "\n" + "Status in QEMU:\n" + " New\n" + "\n" + "Bug description:\n" + " I was trying to configure latencies and bandwidths between nodes in a\n" + " NUMA emulation using QEMU 5.0.0.\n" + "\n" + " Host : Ubuntu 20.04 64 bit\n" + " Guest : Ubuntu 18.04 64 bit\n" + "\n" + " The machine configured has 2 nodes. Each node has 2 CPUs and has been\n" + " allocated 3GB of memory. The memory access latencies and bandwidths\n" + " for a local access (i.e from initiator 0 to target 0, and from\n" + " initiator 1 to target 1) are set as 40ns and 10GB/s respectively. The\n" + " memory access latencies and bandwidths for a remote access (i.e from\n" + " initiator 1 to target 0, and from initiator 0 to target 1) are set as\n" + " 80ns and 5GB/s respectively.\n" + "\n" + " The command line launch is as follows.\n" + "\n" + " sudo x86_64-softmmu/qemu-system-x86_64 \\\n" + " -machine hmat=on \\\n" + " -boot c \\\n" + " -enable-kvm \\\n" + " -m 6G,slots=2,maxmem=7G \\\n" + " -object memory-backend-ram,size=3G,id=m0 \\\n" + " -object memory-backend-ram,size=3G,id=m1 \\\n" + " -numa node,nodeid=0,memdev=m0 \\\n" + " -numa node,nodeid=1,memdev=m1 \\\n" + " -smp 4,sockets=4,maxcpus=4 \\\n" + " -numa cpu,node-id=0,socket-id=0 \\\n" + " -numa cpu,node-id=0,socket-id=1 \\\n" + " -numa cpu,node-id=1,socket-id=2 \\\n" + " -numa cpu,node-id=1,socket-id=3 \\\n" + " -numa dist,src=0,dst=1,val=20 \\\n" + " -net nic \\\n" + " -net user \\\n" + " -hda testing.img \\\n" + " -numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-latency,latency=40 \\\n" + " -numa hmat-lb,initiator=0,target=0,hierarchy=memory,data-type=access-bandwidth,bandwidth=10G \\\n" + " -numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-latency,latency=80 \\\n" + " -numa hmat-lb,initiator=0,target=1,hierarchy=memory,data-type=access-bandwidth,bandwidth=5G \\\n" + " -numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-latency,latency=80 \\\n" + " -numa hmat-lb,initiator=1,target=0,hierarchy=memory,data-type=access-bandwidth,bandwidth=5G \\\n" + " -numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-latency,latency=40 \\\n" + " -numa hmat-lb,initiator=1,target=1,hierarchy=memory,data-type=access-bandwidth,bandwidth=10G \\\n" + "\n" + " Then the latencies and bandwidths between the nodes were tested using\n" + " the Intel Memory Latency Checker v3.9\n" + " (https://software.intel.com/content/www/us/en/develop/articles/intelr-\n" + " memory-latency-checker.html). But the obtained results did not match\n" + " the configuration. The following are the results obtained.\n" + "\n" + " Latency_matrix with idle latencies (in ns)\n" + "\n" + " Numa Node\n" + " . .0. . .1.\n" + " 0 36.2 36.4\n" + " 1 34.9 35.4\n" + "\n" + " Bandwidth_matrix with memory bandwidths (in MB/s)\n" + "\n" + " Numa Node\n" + " . . .0. . . .1. \n" + " 0 15167.1 15308.9\n" + " 1 15226.0 15234.0\n" + "\n" + " A test was also conducted with the tool \342\200\234lat_mem_rd\342\200\235 from lmbench to\n" + " measure the memory read latencies. This also gave results which did\n" + " not match the config.\n" + "\n" + " Any information on why the config latency and bandwidth values are not\n" + " applied, would be appreciated.\n" + "\n" + "To manage notifications about this bug go to:\n" + https://bugs.launchpad.net/qemu/+bug/1888923/+subscriptions -def9e6230bc861054bcddf60c6f86dd3f2938caa2dfb10fd4851c41d5d37a9a8 +ca5b10861ce6469ecca2e8c1d1f0e5374dde99823c6a877d68149cdc25dc505c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.