public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Chris Friesen <cfriesen@nortelnetworks.com>,
	linux-kernel@vger.kernel.org
Subject: Re: No 100 HZ timer ! & the tq_timer
Date: Thu, 02 Aug 2001 15:47:42 -0700	[thread overview]
Message-ID: <3B69D88E.1928D287@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0108021641250.2340-100000@waste.org>

Oliver Xymoron wrote:
> 
> On Thu, 2 Aug 2001, george anzinger wrote:
> 
> > I guess I am confused.  How is it that raising HZ improves throughput?
> > And was that before or after the changes in the time slice routines that
> > now scale with HZ and before were fixed?  (That happened somewhere
> > around 2.2.14 or 2.2.16 or so.)
> 
> My guess is that processes that are woken up for whatever reason get to
> run sooner, reducing latency, and thereby increasing throughput when not
> compute-bound. Presumably this was with shorter time slices.
> 
The only timer dependency I can see on a wake up is related to the
"tq_timer".  This is a tasklet queue that is checked each tick. 
Tasklets that are in it are then run on interrupt exit.  IMHO this whole
list should go away.  If a deferred action is actually needed, a timer
should be used to kick it off.  It should not be hooked to the tick the
way it is.  Better yet, why is it needed at all?

Comments anyone?

George

  reply	other threads:[~2001-08-02 22:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 17:22 No 100 HZ timer ! george anzinger
2001-08-01 19:34 ` Chris Friesen
2001-08-01 19:49   ` Richard B. Johnson
2001-08-01 20:08     ` Mark Salisbury
2001-08-01 20:33     ` george anzinger
2001-08-01 21:20   ` george anzinger
2001-08-02  4:28     ` Rik van Riel
2001-08-02  6:03       ` george anzinger
2001-08-02 14:39         ` Oliver Xymoron
2001-08-02 16:36           ` george anzinger
2001-08-02 17:05             ` Oliver Xymoron
2001-08-02 17:46               ` george anzinger
2001-08-02 18:41                 ` Oliver Xymoron
2001-08-02 21:18                   ` george anzinger
2001-08-02 22:09                     ` Oliver Xymoron
2001-08-02 22:47                       ` george anzinger [this message]
2001-08-02 17:26             ` John Alvord

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=3B69D88E.1928D287@mvista.com \
    --to=george@mvista.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oxymoron@waste.org \
    --cc=riel@conectiva.com.br \
    /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