add 18th iteration of classifier

1 files changed, 72 insertions, 0 deletions

diff --git a/results/classifier/118/performance/1253563 b/results/classifier/118/performance/1253563
new file mode 100644
index 000000000..7fab27a3e
--- /dev/null
+++ b/results/classifier/118/performance/1253563
@@ -0,0 +1,72 @@
+performance: 0.924
+socket: 0.666
+device: 0.645
+graphic: 0.634
+x86: 0.603
+kernel: 0.585
+semantic: 0.564
+architecture: 0.526
+register: 0.513
+network: 0.504
+peripherals: 0.475
+PID: 0.457
+mistranslation: 0.439
+assembly: 0.425
+debug: 0.401
+user-level: 0.394
+permissions: 0.372
+ppc: 0.366
+virtual: 0.361
+hypervisor: 0.348
+vnc: 0.246
+files: 0.209
+arm: 0.206
+KVM: 0.197
+VMM: 0.191
+boot: 0.190
+i386: 0.180
+risc-v: 0.153
+TCG: 0.082
+
+bad performance with rng-egd backend
+
+
+1. create listen socket
+# cat /dev/random | nc -l localhost 1024
+
+2. start vm with rng-egd backend
+
+./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -mon chardev=qmp,mode=control,pretty=on -chardev socket,id=qmp,host=localhost,port=1234,server,nowait -m 2000 -device virtio-net-pci,netdev=h1,id=vnet0 -netdev tap,id=h1 -vnc :0 -drive file=/images/RHEL-64-virtio.qcow2 \
+-chardev socket,host=localhost,port=1024,id=chr0 \
+-object rng-egd,chardev=chr0,id=rng0 \
+-device virtio-rng-pci,rng=rng0,max-bytes=1024000,period=1000
+
+(guest) # dd if=/dev/hwrng of=/dev/null
+
+note: cancelling dd process by Ctrl+c, it will return the read speed.
+
+Problem:   the speed is around 1k/s
+
+===================
+
+If I use rng-random backend (filename=/dev/random), the speed is about 350k/s).
+
+It seems that when the request entry is added to the list, we don't read the data from queue list immediately.
+The chr_read() is delayed, the virtio_notify() is delayed.  the next request will also be delayed. It effects the speed.
+
+I tried to change rng_egd_chr_can_read() always returns 1,  the speed is improved to (about 400k/s)
+
+Problem: we can't poll the content in time currently
+
+
+Any thoughts?
+
+Thanks, Amos
+
+Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+
+Let's close this bug, it's passed 6 years.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+