From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
Subject: Re: Query regarding 2.6.335 RT and Non-RT performance
Date: Thu, 19 Aug 2010 12:14:55 -0700
Message-ID: <4C6D82AF.7020806@gmail.com>
References: <AANLkTik4U-ua1zi5r5n4uw8oA-cQOO0zev__OuCto7CP@mail.gmail.com>	<AANLkTimbQh3rTKnK5cri10_wLJ8BJfUnf54iZ1ENLyuN@mail.gmail.com>	<4C6AC4A6.4080407@redhat.com>	<AANLkTikM5sMtOmu959EZkXUxr=zX8L2HwK52L5JjAK59@mail.gmail.com>	<4C6AE6D7.2060006@us.ibm.com>	<AANLkTimzwSq_8A6vQftOUptpSkhY5nbc37ihx=r=Ff33@mail.gmail.com>	<4C6D46C7.5020209@us.ibm.com>	<1282233963.31855.10.camel@baracus> <AANLkTikFMnr=5=rgU5V7cny5j=ZNLVUJMEewvAOpbpEx@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Nivedita Singhvi <niv@us.ibm.com>,
	David Sommerseth <davids@redhat.com>,
	linux-rt-users@vger.kernel.org
To: Manikandan Ramachandran <crmanik@gmail.com>
Return-path: <linux-rt-users-owner@vger.kernel.org>
Received: from mail-fx0-f46.google.com ([209.85.161.46]:33350 "EHLO
	mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751475Ab0HSTPB (ORCPT
	<rfc822;linux-rt-users@vger.kernel.org>);
	Thu, 19 Aug 2010 15:15:01 -0400
Received: by fxm13 with SMTP id 13so1333804fxm.19
        for <linux-rt-users@vger.kernel.org>; Thu, 19 Aug 2010 12:15:00 -0700 (PDT)
In-Reply-To: <AANLkTikFMnr=5=rgU5V7cny5j=ZNLVUJMEewvAOpbpEx@mail.gmail.com>
Sender: linux-rt-users-owner@vger.kernel.org
List-ID: <linux-rt-users.vger.kernel.org>

  On 08/19/2010 11:15 AM, Manikandan Ramachandran wrote:
> On Thu, Aug 19, 2010 at 9:06 AM, Sven-Thorsten Dietrich
> <thebigcorporation@gmail.com>  wrote:
>> On Thu, 2010-08-19 at 07:59 -0700, Nivedita Singhvi wrote:
>>> On 08/17/2010 03:22 PM, Manikandan Ramachandran wrote:
>>>
>>>
>>>> I see a scenario where higher priority task is ready to run but lower
>>>> priority IRQ thread is hogging the cpu. Please see the timeline log
>>>> below:
>>>>
>>>> GIVE ffff0c1c [Comment: High priority IRQ thread wakes up high
>>>> priority process at jiffy 0xffff0c1c]
>>>> **ffff0c21**##ffff0c21##**ffff0c21**##ffff0c21##**ffff0c21**##ffff0c21##**ffff0c21**##ffff0c21##**ffff0c21**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c22**##ffff0c22##**ffff0c23**##ffff0c23##**ffff0c23**##ffff0c23##**ffff0c23**##ffff0c24##**ffff0c24**##ffff0c24##**ffff0c24**##ffff0c24##
>>>> [Comment: Low priority IDE[ide_intr] handler hogs CPU for almost 3 ms]
>>>> GOTffff0c26 [Comment: High priority task wakes up after 10 ms!!]
>>>>
>>>> I fail to understand why scheduler failed to schedule high priority
>>>> task 10 times in a row. FYI, I have put IDE thread to SCHED_NORMAL
>>>> while high priority thread and task to SCHED_FIFO.
>>> Not really sure from the above what's going on, what priorities
>>> you are running at, etc.
>>>
>>> You might want look at the output of "ps -eLo pid,rtprio,policy,comm"
>>> to see if you can confirm your scheduler attributes.
>>>
>> Also, use the tracing facilities, as its hard to understand your time
>> line and the source of it.
>>
>> I think if your priorities are right, your kernel config is right, and
>> your measurement tool doesn't interfere, 10 ms latency is incredibly
>> unlikely.
>>
>>
>>> thanks,
>>> Nivedita
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> I see many tracing options. Any trace config in particular?
>
>

Steve's latency tracing can generate a time-stamped stack dump of the 
Kernel code-path that blocks the RT task you are trying to run.