DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shirley Avishour <shirley@imvisiontech.com>
To: Jason Kwon <m43kwon@gmail.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] drops while transmitting to the kni using rte_kni_tx_burst()
Date: Mon, 23 Jan 2017 09:59:39 +0200	[thread overview]
Message-ID: <CACn717hv18Vi7Fp5Zumd8=QgvDhR2MUHurcEQKJYBckHZGQBeg@mail.gmail.com> (raw)
In-Reply-To: <CAEo68ap6cF63V2u0DYU7ToFX0Wn3Og3GPm7EcM2gsG-x79nfpQ@mail.gmail.com>

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 <m43kwon@gmail.com> 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 <ferruh.yigit@intel.com>
> 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!
>> >
>>
>>
>

      reply	other threads:[~2017-01-23  7:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 12:20 Shirley Avishour
2017-01-16 14:42 ` Ferruh Yigit
2017-01-16 14:47   ` Shirley Avishour
2017-01-16 14:55     ` Ferruh Yigit
2017-01-16 14:58       ` Shirley Avishour
2017-01-17 17:46         ` Ferruh Yigit
2017-01-17 17:57           ` Ferruh Yigit
2017-01-18  9:51             ` Shirley Avishour
2017-01-16 15:43       ` Shirley Avishour
2017-01-17 12:34         ` Shirley Avishour
2017-01-17 17:49           ` Ferruh Yigit
2017-01-17 14:21       ` Jay Rolette
2017-01-20 19:48   ` Jason Kwon
2017-01-23  7:59     ` Shirley Avishour [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACn717hv18Vi7Fp5Zumd8=QgvDhR2MUHurcEQKJYBckHZGQBeg@mail.gmail.com' \
    --to=shirley@imvisiontech.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=m43kwon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).