From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Softirq preemption
Date: Tue, 06 Dec 2005 20:31:48 -0500 [thread overview]
Message-ID: <1133919109.15592.22.camel@mindpipe> (raw)
In-Reply-To: <1133464131.7898.30.camel@mindpipe>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
On Thu, 2005-12-01 at 14:08 -0500, Lee Revell wrote:
> Ingo,
>
> Is there any chance that the softirq preemption feature from the -rt
> kernel can be pushed upstream?
>
FWIW, here is the longest latency I see with 2.6.14-rt22, with the same
preemption settings as 2.6.14 + PREEMPT. AFAICT a longish network
softirq gets interrupted by several disk and network interrupts which
adds up to ~1ms. Is there any easy way to break up this code path that
could be acceptable for mainline, or does this seem like a reasonable
lower limit on achievable latency (until/unless PREEMPT_RT gets merged
etc)?
Lee
[-- Attachment #2: 2.6.14-rt22-trace.gz --]
[-- Type: application/x-gzip, Size: 7015 bytes --]
next prev parent reply other threads:[~2005-12-07 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 19:08 Softirq preemption Lee Revell
2005-12-07 1:31 ` Lee Revell [this message]
2005-12-07 9:02 ` Ingo Molnar
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=1133919109.15592.22.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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