From: "David S. Miller" <davem@redhat.com>
To: dipankar@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockfree rtcache lookup using RCU
Date: Wed, 08 May 2002 02:09:32 -0700 (PDT) [thread overview]
Message-ID: <20020508.020932.128330582.davem@redhat.com> (raw)
In-Reply-To: <20020508142433.D10505@in.ibm.com>
From: Dipankar Sarma <dipankar@in.ibm.com>
Date: Wed, 8 May 2002 14:24:33 +0530
On Wed, May 08, 2002 at 01:10:08AM -0700, David S. Miller wrote:
> 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 ?
The more common situation is server N IP (where N is 1 or a very small
number), destination clients == thousands of IPs.
So looking up the same dst cache entry with each benchmark client
is very unrealistic. Try a unique IP address for every single lookup.
next prev parent reply other threads:[~2002-05-08 9:22 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
2002-05-08 9:09 ` David S. Miller [this message]
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=20020508.020932.128330582.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