From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: 16-CPU #s for lockfree rtcache (rt_rcu)
Date: Sat, 18 May 2002 02:03:57 +0530 [thread overview]
Message-ID: <20020518020357.B16829@in.ibm.com> (raw)
In-Reply-To: <20020517214433.A15556@in.ibm.com> <20020517.094624.68229633.davem@redhat.com> <m37km2vaoz.fsf@averell.firstfloor.org> <20020517.122519.102199743.davem@redhat.com>
On Fri, May 17, 2002 at 12:25:19PM -0700, David S. Miller wrote:
> From: Andi Kleen <ak@muc.de>
> Date: 17 May 2002 21:25:16 +0200
>
> "David S. Miller" <davem@redhat.com> writes:
>
> > Provide the data, it will be interesting.
>
> I bet the numbers would be much better if the x86
> do_gettimeofday() was converted to a lockless version first ...
> Currently it is bouncing around its readlock for every incoming packet.
>
> That is true. But right now we are trying to analyze the effects of
> his patch all by itself.
Yes, that is a another problem needs addressing.
BTW, do_gettimeofday() also shows up moderately significant in profile
of 8-CPU webserver benchmark. I will address xtime_lock separately.
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
prev parent reply other threads:[~2002-05-17 20:30 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
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 [this message]
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=20020518020357.B16829@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=ak@muc.de \
--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).