From: Nivedita Singhvi <niv@us.ibm.com>
To: Manikandan Ramachandran <crmanik@gmail.com>
Cc: David Sommerseth <davids@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: Query regarding 2.6.335 RT and Non-RT performance
Date: Tue, 17 Aug 2010 12:45:27 -0700 [thread overview]
Message-ID: <4C6AE6D7.2060006@us.ibm.com> (raw)
In-Reply-To: <AANLkTikM5sMtOmu959EZkXUxr=zX8L2HwK52L5JjAK59@mail.gmail.com>
On 08/17/2010 11:24 AM, Manikandan Ramachandran wrote:
> Thanks David& Mark for your valuable input!
>
> I'm not expecting RT kernel to be real fast. However I expect latency
> of higher priority task to be less in RT kernel. I'll run the tests
> that you have suggested and see if there is any inherent issue with my
> system.
Actually, a more accurate statement would be "I expect max latency
of higher priority task to be less in RT kernel."
This is true for max latency as reported by you (max, min):
Stock: 418011us 3s
RT: 366156us 3s
So while the min might reflect the best that the system can do, the
max does seem a tad high -- you do need to look into that.
> One more query, with RT patch is it possible for higher priority task
> to preempt a lower priority IRQ thread [For eg, IDE] ? If so when does
> that happen, during next timer interrupt [Assuming IRQ thread uses
> whole schedule slot and doesn't yield between]?
Yes, and when that higher priority task becomes runnable.
thanks,
Nivedita
next prev parent reply other threads:[~2010-08-17 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik4U-ua1zi5r5n4uw8oA-cQOO0zev__OuCto7CP@mail.gmail.com>
2010-08-17 6:07 ` Query regarding 2.6.335 RT and Non-RT performance Manikandan Ramachandran
2010-08-17 15:54 ` Mark Knecht
2010-08-17 17:19 ` David Sommerseth
2010-08-17 18:24 ` Manikandan Ramachandran
2010-08-17 19:45 ` Nivedita Singhvi [this message]
2010-08-17 22:22 ` Manikandan Ramachandran
2010-08-19 14:59 ` Nivedita Singhvi
2010-08-19 16:06 ` Sven-Thorsten Dietrich
2010-08-19 18:15 ` Manikandan Ramachandran
2010-08-19 19:14 ` Sven-Thorsten Dietrich
2010-08-23 14:26 ` gowrishankar
2010-08-17 20:24 ` Mark Knecht
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=4C6AE6D7.2060006@us.ibm.com \
--to=niv@us.ibm.com \
--cc=crmanik@gmail.com \
--cc=davids@redhat.com \
--cc=linux-rt-users@vger.kernel.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