From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hajime Tazaki Subject: Re: [RFC v2 07/37] lkl: interrupt support Date: Tue, 18 Feb 2020 17:18:41 +0900 Message-ID: References: <567fd4d5c395e2279e86ca0bfca544ad2773a31d.1573179553.git.thehajime@gmail.com> <739ada9a-b88a-5192-fb4b-65132a74b4de@kot-begemot.co.uk> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mail-pg1-f193.google.com ([209.85.215.193]:34615 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbgBRISq (ORCPT ); Tue, 18 Feb 2020 03:18:46 -0500 Received: by mail-pg1-f193.google.com with SMTP id j4so10580418pgi.1 for ; Tue, 18 Feb 2020 00:18:46 -0800 (PST) In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: anton.ivanov@kot-begemot.co.uk Cc: richard.weinberger@gmail.com, linux-arch@vger.kernel.org, tavi.purdila@gmail.com, linux-um@lists.infradead.org, retrage01@gmail.com, linux-kernel-library@freelists.org, sigmaepsilon92@gmail.com Hello, On Wed, 05 Feb 2020 23:24:29 +0900, Hajime Tazaki wrote: > > Make sure you are testing with the vector network devices, the > > legacy ones are scheduled to be obsoleted at some point > > I was aware of the commit to obsolete several backend with the vector > device, but did not include in the patchset and tests. I will try to > do it for the next round. So I added a vector device support, tested with tap backend. Here is a list of numbers with various configurations that v3+ patch have. disclaimer: the experiment is immature, not apple-to-apple in many aspects. So this result only presents one of the parameter set that I took. I will update/clean up later if there are interests. - testbed +--docker0--+ | | 10GbE netperf +---tap0 eth0 +==========+ eth0 +---+ netserver (client) (ixgbe) (ixgbe) <-- Linux box (4.18.5) --> <-- Linux box (4.17.19) --> - setup varied client side (netperf) with different net drivers/devices. tso,tx/rx csum are enabled if possible. - netperf 10secs (Mbps) result |TCP_STREAM | TCP_MAERTS -------------------- -------------------------- UMMODE_LIB (um-tap) | 2290.42 | 1.04 UMMODE_LIB (vec-tap) | 3699.98 | 5682.40 UMMODE_LIB (virtio) | 8029.13 | 9384.78 UMMODE_KERN (um-tap) | 2233.17 | 7.85 UMMODE_KERN (vec-tap)| 5527.37 | 9414.00 # UMMODE_LIB (virtio) isn't included in v3 patches. full output log is here; https://gist.github.com/thehajime/a71878cccf7830a23a23f8f8e8cc8753 result of UMMODE_LIB (vec-tap) is not stable: it sometimes shows over 8Gbps (TCP_STREAM) while most of the times lower. But I suppose UMMODE_LIB with vector driver isn't that bad, though there is still a gap to UMMODE_KERN (vector). -- Hajime