mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: kernwek jalsl <edityacomm@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: softirqd
Date: Tue, 18 Nov 2003 08:31:36 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0311180825240.30076@chaos> (raw)
In-Reply-To: <20031118063551.25057.qmail@web20710.mail.yahoo.com>

On Mon, 17 Nov 2003, kernwek jalsl wrote:

>
> Hi;
>
> Sorry in case I was not very clear with my
> requirements.   With real time interrupt I meant a
> real time task waiting for IO from this interrupt.
> Assume that I have a high priority interrupt and a
> real time task waiting for it. Well followimg are the
> various latencies involved:
> L1- interrupt latency
> L2- hard and soft IRQ completion
> L3 - scheduler latency
> L4 - scheduler completion
>
> L1 is pretty acceptable on Linux. For L3 we have the
> preemption and low latency patch. And for L4 the O(1)
> scheduler solves the problem. So I see L2 as the
> bootleneck especially with soft IRQ since the softIRQs
> get scheduled in a non real time thread and there is
> no wayI can tell the softIRQd that I want highest
> priority for the interrupt that will wake up my real
> time task. I was seeking a solution to this.

The fastest would not use softIRQ at all. As previously
taught, softIRQ is used for things that can be deferred.
You should handle everything in the primary ISR and
issue wake_up_interruptible() from the ISR. You should
be waking anybody sleeping in select() and anybody sleeping
in read().

>
> I know that TimeSYS has as patch for making the
> softIRQ a real time thread as well as giving
> priorities for both the top and bottom halves. Is
> there any place where I can get some performance
> figures for this patch?
>
> Regards
>

Search RTLinux.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-11-18 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  9:45 softirqd kernwek jalsl
2003-11-17 14:42 ` softirqd Richard B. Johnson
2003-11-18  6:35   ` softirqd kernwek jalsl
2003-11-18 13:31     ` Richard B. Johnson [this message]
2003-11-18 22:24     ` softirqd Peter Chubb
2003-11-18 22:44       ` softirqd Richard B. Johnson

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=Pine.LNX.4.53.0311180825240.30076@chaos \
    --to=root@chaos.analogic.com \
    --cc=edityacomm@yahoo.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®