mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: kernwek jalsl <edityacomm@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: softirqd
Date: Tue, 18 Nov 2003 17:44:34 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0311181736170.17786@chaos> (raw)
In-Reply-To: <16314.39961.545212.446223@wombat.chubb.wattle.id.au>

On Wed, 19 Nov 2003, Peter Chubb wrote:

>
>
>
> Kernwek Jalsl said:
>
> Kernwek> Sorry in case I was not very clear with my
> Kernwek> requirements.   With real time interrupt I meant a
> Kernwek> real time task waiting for IO from this interrupt.
> Kernwek> Assume that I have a high priority interrupt and a
> Kernwek> real time task waiting for it. Well followimg are the
> Kernwek> various latencies involved:
> Kernwek> L1- interrupt latency
> Kernwek> L2- hard and soft IRQ completion
> Kernwek> L3 - scheduler latency
> Kernwek> L4 - scheduler completion
>
> Kernwek> L1 is pretty acceptable on Linux.
>
> I've been trying to measure this.  On IA64 I'm measuring around
> 2.5microseconds (on a 900MHz machine).  I personally think that this
> is too big, and could be reduced.


I have a driver which, upon getting an IRQ7 (printer-port interrupt),
just reads the 'paper-out' bit and writes the result to the data-port.
This allows me to toggle the bit and measure the time using a 'scope
and a function generator. The complete time for everything is about
900 nanoseconds on this machine:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 5
model name	: Pentium II (Deschutes)
stepping	: 1
cpu MHz		: 399.568
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr
bogomips	: 797.90

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 5
model name	: Pentium II (Deschutes)
stepping	: 1
cpu MHz		: 399.568
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr
bogomips	: 797.90


I have to disconnect the network before making the test because
the network driver will hog too much CPU time handling broadcast
messages to make any useful measurments.

Considering that it takes 150 to 200 ns to read/write the printer-
port, I don't think that's too bad.


[SNIPPED...]



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 22:41 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     ` softirqd Richard B. Johnson
2003-11-18 22:24     ` softirqd Peter Chubb
2003-11-18 22:44       ` Richard B. Johnson [this message]

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.0311181736170.17786@chaos \
    --to=root@chaos.analogic.com \
    --cc=edityacomm@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    /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®