DPDK usage discussions
 help / color / mirror / Atom feed
From: junlee <lijun422@gmail.com>
To: Jay Rolette <rolette@infinite.io>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] KNI with RTE_KNI_PREEMPT_DEFAULT=n causes CPU soft-lockup
Date: Tue, 28 Nov 2017 10:24:36 +0800	[thread overview]
Message-ID: <CACVZbxodcAyY1ngqwvZ3cTZVprLmufE3BtxhE_j8t=Z1uzBvWg@mail.gmail.com> (raw)
In-Reply-To: <CACVZbxrg1-CE5wQF=YwAHJJaWFK63N5n2j-SEJCB7RVwmzR2fw@mail.gmail.com>

We also tried to turn off the watchdog, then we got RCU stall.
INFO: rcu_sched self-detected stall on CPU

Is there any system configuration that should be made before setting
RTE_KNI_PREEMPT_DEFAULT to n?


2017-11-27 20:49 GMT+08:00 junlee <lijun422@gmail.com>:

> Hi Jay,
>
> Thanks.
> We have read the thread before, increasing HZ to 1000 helps, but we are
> looking for latency even less than 1ms.
> The DPDK version is 17.05.
>
> The kernel preempt setting is:
> CONFIG_PREEMPT_NONE=y
> # CONFIG_PREEMPT_VOLUNTARY is not set
> # CONFIG_PREEMPT is not set
>
> Seems the watchdog/x process could not get chance to run
> when schedule_timeout_interruptible() is not called.
>
> Thanks.
> BR//Wendy
>
> 2017-11-27 20:36 GMT+08:00 Jay Rolette <rolette@infinite.io>:
>
>> That shouldn't cause soft-lockups, but IIRC, there have been KNI bugs in
>> that past that would. Probably worth checking whatever version of DPDK you
>> are running vs. the tree for relevant fixes.
>>
>> Given what you are looking into, this thread may be of interest:
>>
>> http://dpdk.org/ml/archives/dev/2015-June/018858.html
>>
>> Jay
>>
>> On Sun, Nov 26, 2017 at 7:27 PM, junlee <lijun422@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> We are testing KNI performance and finds the
>>> schedule_timeout_interruptible
>>> causes extra latency for packets.
>>>
>>> We tried to set RTE_KNI_PREEMPT_DEFAULT=n to reduce the latency, but ends
>>> up with CPU soft-lockup.
>>>
>>> Anybody knows how to make this work?
>>>
>>> static int
>>> kni_thread_single(void *data)
>>> {
>>> struct kni_net *knet = data;
>>> int j;
>>> struct kni_dev *dev;
>>>
>>> while (!kthread_should_stop()) {
>>> down_read(&knet->kni_list_lock);
>>> for (j = 0; j < KNI_RX_LOOP_NUM; j++) {
>>> list_for_each_entry(dev, &knet->kni_list_head, list) {
>>> kni_net_rx(dev);
>>> kni_net_poll_resp(dev);
>>> }
>>> }
>>> up_read(&knet->kni_list_lock);
>>> #ifdef RTE_KNI_PREEMPT_DEFAULT
>>> /* reschedule out for a while */
>>> schedule_timeout_interruptible(
>>> usecs_to_jiffies(KNI_KTHREAD_RESCHEDULE_INTERVAL));
>>> #endif
>>> }
>>>
>>> return 0;
>>> }
>>>
>>> Thanks.
>>>
>>
>>
>

  reply	other threads:[~2017-11-28  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  1:27 junlee
     [not found] ` <CADNuJVr3O+h-mhiL8=2tJtk0wCecVE_4XfaCog0xpVz10yc5Ew@mail.gmail.com>
2017-11-27 12:49   ` junlee
2017-11-28  2:24     ` junlee [this message]
2017-12-04  9:24       ` junlee

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='CACVZbxodcAyY1ngqwvZ3cTZVprLmufE3BtxhE_j8t=Z1uzBvWg@mail.gmail.com' \
    --to=lijun422@gmail.com \
    --cc=rolette@infinite.io \
    --cc=users@dpdk.org \
    /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).