From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f182.google.com (mail-ot0-f182.google.com [74.125.82.182]) by dpdk.org (Postfix) with ESMTP id ED4842C38 for ; Mon, 23 Jan 2017 08:59:40 +0100 (CET) Received: by mail-ot0-f182.google.com with SMTP id 104so96931685otd.3 for ; Sun, 22 Jan 2017 23:59:40 -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=5WO/zYkWLkD1l85HQv7BwobE6F8rIxYa1UhBbJ55yx8=; b=ZIMcB2IvqfL0GDcNdaBY6LjdhOyOO5KqNbYk8t2r27jg4LcbnxHPJrxvVjKnbZEox4 pXcVwWlHJnf5FNdF1IdjWNCBDXAhstqDGjxencZNfzuH7KsEnwZ2MV/szGmwsBGZtpm3 fT8rqDd5qpcSD991q2SO6IWfE+FY4LSjzgv2iyqmBenrUU2IberoYoN5o2hk7FY4ZkTM LPUUSeeSP8z6nJ1ojFsPK6FSvOFzJYGPYSQ313mQTF+TC0tUN+3kmemA8WZ+LnIU9JLM smJQr87jD2twB6QSJg1hsa6xd9j62oVB++4oeBpS62SDDePxvFb+tydDS5gtlY2x4JwM C5fw== 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=5WO/zYkWLkD1l85HQv7BwobE6F8rIxYa1UhBbJ55yx8=; b=GQhyAEpN2oSTmnBg/NXah5kq0PbVxi4YOmaHCsrQFpnIBp74IGruOrjnoHGvsSTwvj oJdt7xycTgT0U5+6snVLVcA7v2i2alQBsUsVhJWvdyK+7GesDaFlSwv3vqVUZeuEYJeo /noKH5SvnDz37ypXQjArYCqcCi7DrumApaAqLRBWW6ne3zSlwc4mUQ5DSql+Gg3UVDKw /8VQf8+Pnuo4c+vbQGegAs3wtHfdjCET5INA+PNRkYAGIXsApQSaCax1lBCyuBMtPM4s xwBbWR2EvbVGzFW5Qhc4217YIToD5pf3zFaPRbOJlcmKQyfUzxfa3LhnlDxzOkeNMiOL L7aw== X-Gm-Message-State: AIkVDXKDUKyW5Z3rja9VKAipLl8wSfmQFNR/eshJWwnx6xc4hHX8nWTeyp7eWksDX+x2z3PlKmM1SrkeLaTdrQ== X-Received: by 10.157.5.6 with SMTP id 6mr12830606otw.209.1485158380253; Sun, 22 Jan 2017 23:59:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.50.70 with HTTP; Sun, 22 Jan 2017 23:59:39 -0800 (PST) In-Reply-To: References: From: Shirley Avishour Date: Mon, 23 Jan 2017 09:59:39 +0200 Message-ID: To: Jason Kwon Cc: Ferruh Yigit , 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, 23 Jan 2017 07:59:41 -0000 Hi Jason, You are right but I've tried to work in multiple mode as well and it did not change the result. I hope this issue will be solved. Thanks, Shirley. On Fri, Jan 20, 2017 at 9:48 PM, Jason Kwon wrote: > Sorry to hijack the thread, but I was wondering, is the binding of the KNI > kernel thread only applicable in multiple kthread mode? Does it apply in > single kernel thread mode? Looking at the 16.07.2 source, I saw the > following: > > /** > * Create a new kernel thread for multiple mode, set its core > affinity, > * and finally wake it up. > */ > if (multiple_kthread_on) { > kni->pthread = kthread_create(kni_thread_multiple, > (void *)kni, > "kni_%s", kni->name); > if (IS_ERR(kni->pthread)) { > kni_dev_remove(kni); > return -ECANCELED; > } > if (dev_info.force_bind) > kthread_bind(kni->pthread, kni->core_id); > wake_up_process(kni->pthread); > } > > Thanks, > > Jason > > On Mon, Jan 16, 2017 at 6:42 AM, 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! >> > >> >> >