linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 16-CPU #s for lockfree rtcache (rt_rcu)
Date: Fri, 17 May 2002 21:44:33 +0530	[thread overview]
Message-ID: <20020517214433.A15556@in.ibm.com> (raw)
In-Reply-To: <20020517192116.G12631@in.ibm.com> <20020517.064921.80183164.davem@redhat.com>

On Fri, May 17, 2002 at 06:49:21AM -0700, David S. Miller wrote:
>    From: Dipankar Sarma <dipankar@in.ibm.com>
>    Date: Fri, 17 May 2002 19:21:16 +0530
>    
>    2.5.3 : ip_route_output_key [c01bab8c]: 12166
>    2.5.3+rt_rcu : ip_route_output_key [c01bb084]: 6027
>    
> Thanks for doing the testing.  Are you able to do this
> test on some 4 or 8 processor non-NUMA system?

Yes, but may not have been the same test. We have been doing various 
configurations for this test. One fallout of using large number of 
dest addresses is that we have frequent neighbor table garbage collection 
which results in a lot of lock contentions. By slowing down
the packet rate and/or increasing the gc threshold, we can
avoid this. How realistic is this ? If we avoid frequent
gc, we see better gains in route lookup. With frequent gc,
the speedup was of about 22% for an 8 cpu SMP, IIRC. I will rerun
the tests tomorrow or monday to get both sets of numbers for 8-cpu
SMP.

Thanks
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.

  reply	other threads:[~2002-05-17 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 13:51 16-CPU #s for lockfree rtcache (rt_rcu) Dipankar Sarma
2002-05-17 13:49 ` David S. Miller
2002-05-17 16:14   ` Dipankar Sarma [this message]
2002-05-17 16:46     ` David S. Miller
2002-05-17 19:25       ` Andi Kleen
2002-05-17 19:25         ` David S. Miller
2002-05-17 20:33           ` 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=20020517214433.A15556@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).