From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by dpdk.org (Postfix) with ESMTP id D9A917F6D for ; Mon, 25 Jan 2016 14:15:34 +0100 (CET) Received: by mail-qg0-f47.google.com with SMTP id e32so108302444qgf.3 for ; Mon, 25 Jan 2016 05:15:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=eohsMGZg08ztksJIkEx1VnmDdB2xhvYecFkHLqe3LjU=; b=BGTf+RL0K9F/PoFR1orhKE0MvgeSgDjXtQ4N+L6GHL0G9p3WUXuhxtM5NAlqf1x6gD OTYPAtsTuBvMbkLnkUMJ/JBjSXaOAfGUN/AGRHy6ReMwhgr3Z/WRlPZjB0Eckca6HlIP iAl/XievuLcnsdbbsbcuT3jZYCWRm2lIQW7jfjXnGGduRflY05H4LN7aANNKAETF9yxH j2Qpmrvppqg8wLT5+QCHMHVo50Yv0kGOvuiL17y3m17rghOjTDb79JzdVIQiTb6RvXDY e3ePn/P/oc7NHBTGJhfcZ8jea3NzpXDRVH+U5O+R8NMBdkBos9US+m6zQwzaMFjkdpby Hscg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=eohsMGZg08ztksJIkEx1VnmDdB2xhvYecFkHLqe3LjU=; b=FsiakbCjve15IC1HXtcfShq7q489WgS0n/lVEBd3mkALgZiOn7bX5EW2FJzjgnywsI jTlDqsx473pkA8aA3bTnf4BNpKVtcsh9EtdAJQxe4sRPSdELZS/3fBB2mvOpxWyZ64s2 stzz8SQQJJTPshZqZfzjPtY/ywTmcdgBIQwPSI3aFSGjA0TUQk2uiuhVsgvSWEdZlhBS Z1qlbK/SdtC88rFBMplRsDvZUPZyfqK4InNJIWRrYnnbLw+w9YGfgGSKM0XDx2UGggqA +vzRXMeR7/gGQp2mcK2P/6y3YjTwVQnyiMfB+DvnIEJBykOHBabXrQ7tDVbyJQ4Jp1OJ 8t3w== X-Gm-Message-State: AG10YORn+5np3KsF5hsrLUY/vWdi4U766NFdVPt8uHdmgo3AMdUKstipF8bo8u+s+HKIU99i6IG4/q3YFEdW2g== X-Received: by 10.140.143.68 with SMTP id 65mr22354361qhp.25.1453727734372; Mon, 25 Jan 2016 05:15:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Masoud Moshref Javadi Date: Mon, 25 Jan 2016 13:15:24 +0000 Message-ID: To: "Freynet, Marc (Nokia - FR)" , "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] high jitter in dpdk kni X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2016 13:15:35 -0000 I see. But this should not be the issue in Ping. By the way, I checked the timestamps of sending and receiving times at the kni sample application (kni_ingress and kni_egress methods). The RTT at that level is OK (0.1ms) and it seems the jitter comes from the kni kernel module. On Mon, Jan 25, 2016 at 12:29 AM Freynet, Marc (Nokia - FR) < marc.freynet@nokia.com> wrote: > Hi, > > Some months ago we had a problem with the KNI driver. > Our DPDK application forwards to the Linux kernel through KNI the SCTP PD= U > received from the Eth NIC. > In one configuration, the SCTP port Source and Destination were constant > on all SCTP connections. > This is a known SCTP issue as in the multi processor environment, the SCT= P > stack uses the port Source and Destination to hash the processor that wil= l > run the SCTP context in the kernel. > SCTP cannot use the IP address as a hash key thanks to the SCTP multi > homing feature. > > As all SCTP PDU on all SCTP connections where processed by the same Core, > this creates a bottle neck and the KNI interface starts creating Jitter a= nd > even was losing PDU when sending the SCTP PDU to the IP Linux kernel stac= k. > > I am wondering if in a previous release it you not be possible to add KNI > a kind of load sharing with different queues on different cores to forwar= d > the received PDU to the IP Linux stack. > > =E2=80=8B"Bowl of rice will raise a benefactor, a bucket of rice will rai= se a > enemy.", Chinese proverb. > > FREYNET Marc > Alcatel-Lucent France > Centre de Villarceaux > Route de Villejust > 91620 NOZAY France > > Tel: +33 (0)1 6040 1960 > Intranet: 2103 1960 > > marc.freynet@nokia.com > > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of EXT Masoud > Moshref Javadi > Sent: samedi 23 janvier 2016 15:18 > To: users@dpdk.org > Subject: [dpdk-users] high jitter in dpdk kni > > I see jitter in KNI RTT. I have two servers. I run kni sample application > on one, configure its IP and ping an external interface. > > sudo -E build/kni -c 0xaaaa -n 4 -- -p 0x1 -P --config=3D"(0,3,5)" > sudo ifconfig vEth0 192.168.1.2/24 > ping 192.168.1.3 > > This is the ping result: > 64 bytes from 192.168.1.2: icmp_seq=3D5 ttl=3D64 time=3D1.93 ms > 64 bytes from 192.168.1.2: icmp_seq=3D6 ttl=3D64 time=3D0.907 ms > 64 bytes from 192.168.1.2: icmp_seq=3D7 ttl=3D64 time=3D3.15 ms > 64 bytes from 192.168.1.2: icmp_seq=3D8 ttl=3D64 time=3D1.96 ms > 64 bytes from 192.168.1.2: icmp_seq=3D9 ttl=3D64 time=3D3.95 ms > 64 bytes from 192.168.1.2: icmp_seq=3D10 ttl=3D64 time=3D2.90 ms > 64 bytes from 192.168.1.2: icmp_seq=3D11 ttl=3D64 time=3D0.933 ms > > The ping delay between two servers without kni is 0.170ms. > I'm using dpdk 2.2. > > Any thought on how to keep KNI delay predictable? > > Thanks >