From: Mark Mielke <mark@mark.mielke.cc>
To: Linux <linux-kernel@vger.kernel.org>
Subject: Whoa... (was: Re: HZ, preferably as small as possible)
Date: Thu, 11 Jul 2002 09:36:20 -0400 [thread overview]
Message-ID: <20020711093620.A19422@mark.mielke.cc> (raw)
In-Reply-To: <20020710160921.H32168@host110.fsmlabs.com>; from cort@fsmlabs.com on Wed, Jul 10, 2002 at 04:09:21PM -0600
On Wed, Jul 10, 2002 at 04:09:21PM -0600, Cort Dougan wrote:
> Yes, please do make it a config option. 10x interrupt overhead makes me
> worry. It lets users tailor the kernel to their expected load.
All this talk is getting to me.
I thought we recently (1 month ago? 2 months ago?) concluded that
increases in interrupt frequency only affects performance by a very
small amount, but generates an increase in responsiveness. The only
real argument against that I have seen, is the 'power conservation'
argument. The idea was, that the scheduler itself did not execute
on most interrupts. The clock is updated, and that is about all.
I can invent a reason as to why throughput increases, from user space.
The hard drive sends data to the kernel, the kernel handles the
hardware interrupt, grabs the buffer, and returns control to the
active process/thread. It may be some time until the process/thread
that is *reading* the data gets scheduled. Any reduction in the
average time a process/thread will be scheduled to execute, results in
increased throughput.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-07-11 13:39 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 19:59 HZ, preferably as small as possible Grover, Andrew
2002-07-10 21:09 ` george anzinger
2002-07-11 6:03 ` Hannu Savolainen
2002-07-11 7:15 ` george anzinger
2002-07-12 0:36 ` Stevie O
2002-07-12 0:50 ` Thunder from the hill
2002-07-12 0:55 ` Robert Love
2002-07-12 0:58 ` Thunder from the hill
2002-07-12 1:24 ` Alan Cox
2002-07-12 1:37 ` Mark Hahn
2002-07-12 1:09 ` george anzinger
2002-07-12 1:26 ` Roland Dreier
2002-07-12 17:30 ` george anzinger
2002-07-12 1:35 ` Stevie O
2002-07-12 3:01 ` Bernd Eckenfels
2002-07-11 12:54 ` Thunder from the hill
2002-07-11 15:59 ` Martin Dalecki
2002-07-10 21:28 ` Andrew Morton
2002-07-10 21:35 ` Benjamin LaHaise
2002-07-10 21:38 ` Andrew Morton
2002-07-10 21:42 ` Benjamin LaHaise
2002-07-11 2:14 ` CaT
2002-07-11 17:01 ` Martin Dalecki
2002-07-10 22:01 ` Thunder from the hill
2002-07-10 22:09 ` Cort Dougan
2002-07-11 13:36 ` Mark Mielke [this message]
2002-07-11 21:08 ` Whoa... (was: Re: HZ, preferably as small as possible) Daniel Phillips
2002-07-10 22:41 ` HZ, preferably as small as possible Thunder from the hill
2002-07-10 22:47 ` Thunder from the hill
2002-07-10 22:49 ` Eli Carter
2002-07-10 23:05 ` Thunder from the hill
2002-07-10 23:08 ` Dave Mielke
2002-07-10 23:13 ` Thunder from the hill
2002-07-10 23:50 ` J.A. Magallon
2002-07-11 0:28 ` Lincoln Dale
2002-07-11 11:35 ` Kasper Dupont
2002-07-11 12:30 ` Alan Cox
2002-07-11 13:37 ` Kasper Dupont
2002-07-11 15:46 ` Alan Cox
2002-07-11 18:51 ` george anzinger
2002-07-15 5:06 ` Linus Torvalds
2002-07-15 16:26 ` Robert Love
2002-07-15 18:56 ` Linus Torvalds
2002-07-15 19:52 ` mbs
2002-07-15 20:01 ` yodaiken
2002-07-16 11:41 ` Vojtech Pavlik
2002-07-17 19:33 ` Daniel Phillips
2002-07-17 20:31 ` Richard B. Johnson
2002-07-17 20:40 ` Daniel Phillips
2002-07-17 21:02 ` Richard B. Johnson
2002-07-17 21:02 ` Linus Torvalds
2002-07-17 21:16 ` Daniel Phillips
2002-07-18 12:57 ` Richard B. Johnson
2002-07-18 13:25 ` Daniel Phillips
2002-07-18 10:10 ` Kai Henningsen
2002-07-17 20:55 ` Linus Torvalds
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=20020711093620.A19422@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--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®