From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockfree rtcache lookup using RCU
Date: Wed, 8 May 2002 14:24:33 +0530 [thread overview]
Message-ID: <20020508142433.D10505@in.ibm.com> (raw)
In-Reply-To: <20020508125711.B10505@in.ibm.com> <20020508.011008.107273722.davem@redhat.com>
On Wed, May 08, 2002 at 01:10:08AM -0700, David S. Miller wrote:
> From: Dipankar Sarma <dipankar@in.ibm.com>
> Date: Wed, 8 May 2002 12:57:11 +0530
>
> For 1 to 8 CPUs I used the test script
> to send a fixed number of packets to a single destination address.
> The results show that time needed for lookup continuously increases
> for 2.5.3 wherease for rt_rcu-2.5.3, it remains constant.
>
> How does it perform for a write-heavy workload such
> as a massive route flap?
Can you suggest a test to do this ? I can't think of anything other
than manually flushing the route cache.
>
> Both are equally important.
Yes. With RCU, the write-side doesn't affect the performance
of the read-side. However, there is the additional overhead
of calling call_rcu() and queueing up of the RCU callback
for every dst entry that is freed. The other aspect is of
latency, how quickly the deferred rcu callbacks are invoked.
We have done some studies in this regard under various
degrees of workloads. I will put up the graphs in lse. They
will also be presented at OLS2002.
>
> Also, workload for single destination isn't all that interesting
> since such a workload isn't all that common except in benchmarking.
A heavily loaded webserver with NATed ip addresses. Would this not
result in many server processes looking up the same ip address ?
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-08 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 7:27 [PATCH] lockfree rtcache lookup using RCU Dipankar Sarma
2002-05-08 8:10 ` David S. Miller
2002-05-08 8:54 ` Dipankar Sarma [this message]
2002-05-08 9:09 ` David S. Miller
2002-05-08 13:24 ` Dipankar Sarma
2002-05-08 13:45 ` David S. Miller
2002-05-14 11:42 ` Dipankar Sarma
2002-05-08 9:40 ` [PATCH] Completely honor prctl(PR_SET_KEEPCAPS, 1) Dax Kelson
2002-05-08 13:42 ` Keith Owens
2002-05-08 19:28 ` chris
2002-05-08 19:38 ` chris
2002-05-08 19:55 ` Dax Kelson
2002-05-08 20:17 ` Alan Cox
2002-05-08 21:20 ` chris
2002-05-08 21:29 ` Dax Kelson
2002-05-08 20:21 ` [RFC] Making capabilites useful with legacy apps Dax Kelson
2002-05-13 12:55 ` Pavel Machek
2002-05-13 20:28 ` Neil Schemenauer
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=20020508142433.D10505@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