public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	<linux-rt-users@vger.kernel.org>, "Li Zefan" <lizefan@huawei.com>,
	Zhangwei <jovi.zhangwei@huawei.com>
Subject: Re: [BUGREPORT] Tasklet scheduled issue in Linux 3.4.x-rt
Date: Tue, 1 Apr 2014 10:24:18 +0800	[thread overview]
Message-ID: <533A2352.7000306@huawei.com> (raw)
In-Reply-To: <53394296.5030906@linutronix.de>

>> Because this patch does not exist in the latest Linus kernel, so I
>> have not reported this issue to kernel bugzilla.
> 
> This patch exists in all -RT releases up to 3.12. If there is an issue
> with it, it should be solved.
> 
> If the sched bit set is and you can't get lock later then the tasklet
> has be to active. Finally, not getting the lock in the tasklet code
> itself means it is still occupied by the "add-to-the-list" part which
> actually can't happen according to the code.
> You said, that you have an eight-way. Is this also NUMA? If so, does
> this problem happen if you disable NUMA (i.e. run only one NUMA node
> and use only the memory that is directly attached to the node).

Hi Sebastian,
   The target platform is not NUMA, there is only one node.

Thanks!
Yijing.

> 
> 


-- 
Thanks!
Yijing


  reply	other threads:[~2014-04-01  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  9:24 [BUGREPORT] Tasklet scheduled issue in Linux 3.4.x-rt Yijing Wang
2014-03-28 16:37 ` Sebastian Andrzej Siewior
2014-03-29  6:35   ` Yijing Wang
2014-03-31 10:25     ` Sebastian Andrzej Siewior
2014-04-01  2:24       ` Yijing Wang [this message]
2014-03-31 20:50 ` Thomas Gleixner
2014-04-01  3:15   ` Yijing Wang

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=533A2352.7000306@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=bigeasy@linutronix.de \
    --cc=jovi.zhangwei@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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