public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] scalable timers implementation, 2.4.16, 2.5.0
Date: Thu, 6 Dec 2001 08:29:49 +1100	[thread overview]
Message-ID: <20011206082949.400dffd5.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0111271543410.16419-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0111271543410.16419-100000@localhost.localdomain>

On Tue, 27 Nov 2001 15:57:03 +0100 (CET)
Ingo Molnar <mingo@elte.hu> wrote:

> 
> the 'ultra scalable timers' patch, against 2.4.16 or 2.5.0 is available
> at:
> 
>   http://redhat.com/~mingo/scalable-timers-patches/smptimers-2.4.16-A0

Hi Ingo,

	Hmm... there are some ugly hoops there to make sure that they don't
conflict with bottom halves or cli().  I assume you want to take that out:
what will break if that happens, and do we need a disable_timers() interface
to move code over?

Cheers,
Rusty.
PS.  Also would be nice to #define del_timer del_timer_sync, and have a
     del_timer_async for those (very few) cases who really want this.
--
  Anyone who quotes me is an idiot -- Rusty Russell.

  reply	other threads:[~2001-12-05 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27 14:57 [patch] scalable timers implementation, 2.4.16, 2.5.0 Ingo Molnar
2001-12-05 21:29 ` Rusty Russell [this message]
2001-12-05 22:13   ` Andrew Morton
2001-12-06  2:15     ` Rusty Russell
2001-12-06  4:20       ` Andrew Morton
2001-12-06  9:10       ` Alan Cox
2001-12-06 10:41   ` Ingo Molnar
     [not found] <3C0E9BFD.BC189E17@zip.com.au.suse.lists.linux.kernel>
     [not found] ` <E16Bo4c-00031f-00@wagner.suse.lists.linux.kernel>
2001-12-06  2:32   ` Andi Kleen

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=20011206082949.400dffd5.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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