From: Dipankar Sarma <dipankar@in.ibm.com>
To: Ingo Molnar <mingo@redhat.com>
Cc: Christoph Hellwig <hch@ns.caldera.de>,
Andrea Arcangeli <andrea@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Paul McKenney <paul.mckenney@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New Read-Copy Update patch
Date: Wed, 6 Feb 2002 00:11:13 +0530 [thread overview]
Message-ID: <20020206001113.C427@in.ibm.com> (raw)
In-Reply-To: <200202051654.g15GsWH01780@ns.caldera.de> <Pine.LNX.4.44.0202051156300.7240-100000@devserv.devel.redhat.com>
In-Reply-To: <Pine.LNX.4.44.0202051156300.7240-100000@devserv.devel.redhat.com>; from mingo@redhat.com on Tue, Feb 05, 2002 at 11:57:07AM -0500
On Tue, Feb 05, 2002 at 11:57:07AM -0500, Ingo Molnar wrote:
>
> On Tue, 5 Feb 2002, Christoph Hellwig wrote:
>
> > > 3. A per-cpu timer support ? - This will allow us to get rid of the krcud
> > > stuff and make RCU even simpler.
> >
> > Something like http://people.redhat.com/mingo/scalable-timers-patches/smptimers-2.4.16-A0?
> >
> > Ingo, Linus: Any chance to see that in 2.5 soon?
>
> i'll post an updated smptimers patch soon after the scheduler has settled
> down.
Hi Ingo,
Unless you have new code that updates the patch, I can take a stab
at porting it to 2.5. Let me know if that is ok.
Thanks
Dipankar
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-02-05 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 15:48 [PATCH] New Read-Copy Update patch Dipankar Sarma
2002-02-05 16:54 ` Christoph Hellwig
2002-02-05 16:57 ` Ingo Molnar
2002-02-05 18:41 ` Dipankar Sarma [this message]
2002-02-05 18:17 ` Dipankar Sarma
2002-02-05 17:13 ` Andrea Arcangeli
2002-02-05 18:34 ` Dipankar Sarma
2002-02-06 8:44 ` Daniel Phillips
2002-02-06 8:53 ` Dipankar Sarma
2002-02-06 8:58 ` Daniel Phillips
2002-02-06 10:47 ` [PATCH] New Read-Copy Update patch [fixed] Dipankar Sarma
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=20020206001113.C427@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=andrea@suse.de \
--cc=hch@ns.caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.mckenney@us.ibm.com \
--cc=rusty@rustcorp.com.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