Hi Zihan, The numbers on the benchmark are one fastpath, one slowpath (the details show that the length of the IPC is 10, and any messages > 4 go to the slowpath as they will not fit in registers).
I'm going to look at getting these numbers updated with more details for reproducability - is there anything specific you need to know? I don't think we have a kabylake to test on. Note that the numbers are very sensitive to compiler version kernel configuration (especially on x86 if the meldown mitigations are enabled). Cheers, Anna. ________________________________________ From: Devel <devel-bounces@sel4.systems> on behalf of Zihan Yang <whois.zihan.y...@gmail.com> Sent: Tuesday, 7 August 2018 5:39 PM To: devel@sel4.systems Subject: [seL4] Questions about sel4bench IPC statistic in the website Hi, Your website(https://sel4.systems/About/Performance/home.pml) lists the IPC benchmark result, and I wonder is the x64 result for both fastpath, or both slowpath, or one fastpath and the other slowpath? According to the evaluation of my own on x64 kabylake, the fastpath client->server takes about 600 cycles, and slow path client->serve takes over 1100 cycles. But the website data is 1465 and 780, but it does not show whether it is fastpath or slow path. It looks like that the website data has client->server goes into slowpath(maybe because of lower priority), and the server->client goes into fastpath. Is it so? Thanks, Zihan _______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel _______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
