From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org,
Paul McKenney <paul.mckenney@us.ibm.com>,
Andrea Arcangeli <andrea@suse.de>
Subject: Re: 8-CPU (SMP) #s for lockfree rtcache
Date: Tue, 28 May 2002 18:28:06 +0530 [thread overview]
Message-ID: <20020528182806.A21303@in.ibm.com> (raw)
In-Reply-To: <20020528171104.D19734@in.ibm.com> <20020528.042514.92633856.davem@redhat.com>
On Tue, May 28, 2002 at 04:25:14AM -0700, David S. Miller wrote:
> From: Dipankar Sarma <dipankar@in.ibm.com>
> Date: Tue, 28 May 2002 17:11:04 +0530
>
> Here are the results in terms of profile counts in
> ip_route_output_key() - gc stands for neighbor table garbage
> collection adjustment and u2000 stands for 2ms packet
> rate delay. All measurements where done based on 2.5.3 kernel.
>
> Thanks, I am convinced RCU is the way to go.
>
> Once the generic RCU bits are in the 2.5.x tree, feel free to
> send me your ipv4 routing cache changes.
Well, the last time RCU was discussed, Linus said that he would
like to see someplace where RCU clearly helps.
Linus, would you consider this to be such a case and consider
including the rcu_poll patch from aa series of kernels ? It
has been a part of aa kernels for quite a while now. The latest
RCU patches support preemption and AFAICS, new module unloading
and cpu hotplug frameworks can use the RCU synchronize_kernel()
interface.
Or atleast, we can perhaps discuss RCU and see if there are
potential issues that have not been disected so far.
Thanks
--
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-05-28 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 11:41 8-CPU (SMP) #s for lockfree rtcache Dipankar Sarma
2002-05-28 11:25 ` David S. Miller
2002-05-28 12:58 ` Dipankar Sarma [this message]
2002-05-28 12:40 ` David S. Miller
2002-05-28 15:45 ` Andi Kleen
2002-05-28 17:03 ` Alan Cox
2002-05-28 16:34 ` Andi Kleen
2002-05-28 18:10 ` Alan Cox
2002-05-28 17:24 ` Andi Kleen
2002-05-29 4:44 ` Rusty Russell
2002-05-28 15:49 ` Robert Love
2002-05-28 16:25 ` Dipankar Sarma
2002-05-28 17:09 ` Dipankar Sarma
2002-05-29 17:44 ` kuznet
2002-06-03 12:08 ` Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 19:57 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=20020528182806.A21303@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@us.ibm.com \
--cc=torvalds@transmeta.com \
/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