All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dipankar Sarma <dipankar@gamebox.net>,
	Matthew Wilcox <willy@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Run timers as softirqs, not tasklets
Date: Mon, 18 Nov 2002 14:29:10 -0800	[thread overview]
Message-ID: <3DD969B6.9D221DB1@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211172108160.12550-100000@localhost.localdomain

Ingo Molnar wrote:
> 
> On Mon, 18 Nov 2002, Dipankar Sarma wrote:
> 
> > I wrote that part of smptimers to run the per-CPU lists from per-CPU
> > tasklets while porting Ingo's code to 2.5 and Ingo just included it. At
> > that time, it didn't seem necessary to use up a softirq vector when it
> > could be easily done using tasklets.
> 
> i think a separate timer softirq is justified, timers are important
> enough.
> 
>         Ingo
> 
So then, is there any reason to not put them ahead of
HI_SOFTIRQ?  I.e.:

 enum
 {
        TIMER_SOFTIRQ=0,
      	HI_SOFTIRQ
        NET_TX_SOFTIRQ,
        NET_RX_SOFTIRQ,
        SCSI_SOFTIRQ,
-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

  reply	other threads:[~2002-11-18 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 17:16 [PATCH] Run timers as softirqs, not tasklets Matthew Wilcox
2002-11-17 18:46 ` Dipankar Sarma
2002-11-17 20:09   ` Ingo Molnar
2002-11-18 22:29     ` george anzinger [this message]
2002-11-18 22:34       ` Matthew Wilcox
2002-11-17 19:23 ` 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=3DD969B6.9D221DB1@mvista.com \
    --to=george@mvista.com \
    --cc=dipankar@gamebox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.