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

   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?

Basically halfing the profile hits for this function
is wonderful and I'd love to see how much of this translates to a
non-NUMA system.

   I have seen moderately significant profile counts
   for ip_route_input() in preliminary webserver benchmark runs.
   It is not however clear to me that bucket lock cache line
   bouncing is the reason behind it. That one needs more investigation.

This is where most of the routing heavy work is done on
a web server, so this doesn't surprise me.  Once packet
is input and routed, we have destination and just grab a reference to
and use it for output back to that remote host.

  reply	other threads:[~2002-05-17 14:02 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 [this message]
2002-05-17 16:14   ` Dipankar Sarma
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=20020517.064921.80183164.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=dipankar@in.ibm.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).