From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by dpdk.org (Postfix) with ESMTP id CAB13DE5 for ; Mon, 16 Jan 2017 15:47:19 +0100 (CET) Received: by mail-oi0-f50.google.com with SMTP id m124so65427141oif.1 for ; Mon, 16 Jan 2017 06:47:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imvisiontech-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ULVV+ZsvDs50TW6uEH4Veb7OZWpRDcYwL1T7/YR7NIo=; b=2E6xdZw46JVMzyPFzVQep4vdk5knUJXsddFC9ANWr3HY1eea3o2hqlsFwjWR/iHO86 tSdpnG6HVF6Pb8m3LYQ8+PF+FOtIQvGrq0GdOwEkmDZ/a9Nn564ThEox6Z1VxDKR2D9h AIQIb6K2Vu5ugrHoZ/x+c8y8oDOtYKg21UlUIqqPDBGMBWlsnlPOceXGGxyORlm0ndnE XPdnyHQH0cjwThocW7iAIcflGIeMBnh+uCD7zIvSuf87szd4gNriiIxChnvYCISfw187 PmsSLEXqBHB4tUVeuxrYzBol9thBY78YWCzpJALFyT/rWtlLCfylVTzJrxI6cKInXHE+ Ne5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ULVV+ZsvDs50TW6uEH4Veb7OZWpRDcYwL1T7/YR7NIo=; b=glQ1A9nh+6RoYWVRZRfTh9+0Xfm5lBWS9jBqjjxUwggsuaHA3k0SRJGS37B/zOFgfH R74BDtrHdYjvwT/SfxEVY7KoPGMc7WXEwv7yvwPGrQsOl4Dqe3iIoyEaCgAEq17ovn9O png2TVPyiyMHVnS+69pLkzlRdWxUUs//mDqqSSl1JqGkBQ59qPsBDvFF3kWIjZKKNjLo FuiWScpHydb8FBWaE9wPyT1Az8p4+x3emHPkuHcmFB+2dk5tNvCL7Lc1DV9nFOKQ5xJi iSaVBVKIK8z7Y/G6mn5J2YxtrwesJUA3aU98vj19eFKoZCtoC2bu73r0yJPLEU0S70iw 3Ljw== X-Gm-Message-State: AIkVDXKxPRpxoCmluPtLksZiz1Rg0/wNlILbjezzknUVl4laOi0GBkd3BZWd6STOQxbe70Cl4V75DcFb9Zaciw== X-Received: by 10.157.11.13 with SMTP id a13mr17923564ota.82.1484578038860; Mon, 16 Jan 2017 06:47:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.50.70 with HTTP; Mon, 16 Jan 2017 06:47:18 -0800 (PST) In-Reply-To: References: From: Shirley Avishour Date: Mon, 16 Jan 2017 16:47:18 +0200 Message-ID: To: Ferruh Yigit Cc: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] drops while transmitting to the kni using rte_kni_tx_burst() X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2017 14:47:20 -0000 Hi, As I wrote the kernel thread runs on a dedicated lcore. running top while my application is running I see kni_single and the cpu usage is really low... Is there any rate limitation for transmitting to the kernel interface (since packets are being copied in the kernel). On Mon, Jan 16, 2017 at 4:42 PM, Ferruh Yigit wrote: > On 1/16/2017 12:20 PM, Shirley Avishour wrote: > > Hi, > > I have an application over dpdk which is consisted of the following > threads > > each running on a separate core: > > 1) rx thread which listens on in a poll mode for traffic > > 2) 2 packet processing threads (for load balancing) > > 3) kni thread (which also runs on a separate core). > > This is kernel thread, right? Is it bind to any specific core? > Is it possible that this thread shares the core with 2nd processing > thread when enabled? > > > > > the rx thread receives packets and clones them and transmit a copy to the > > kni and the other packet is sent to the packet processing unit (hashing > > over 2 threads). > > the receive traffic rate is 100Mbps. > > When working with single packet processing thread I am able to get all > the > > 100Mbps towards the kni with no drops. > > but when I activate my application with 2 packet processing threads I > start > > facing drops towards the kni. > > the way I see it the only difference now is that I have another threads > > which handles an mbuf and frees it once processing is completed. > > Can anyone assist with this case please? > > > > Thanks! > > > >