From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com,
linux-kernel@vger.kernel.org
Subject: Re: Fw: potential /dev/urandom scalability improvement
Date: Thu, 25 Mar 2004 22:07:10 -0600 [thread overview]
Message-ID: <20040326040710.GF8366@waste.org> (raw)
In-Reply-To: <20040325180014.29e40b65.akpm@osdl.org>
On Thu, Mar 25, 2004 at 06:00:14PM -0800, Andrew Morton wrote:
> David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >
> > The
> > patch below is updated to go on top of your patch and gives about the
> > same performance as I reported yesterday. For now, I defined an
> > inline prefetch_range(). If and when all architectures get updated to
> > define this directly, we can simply remove prefetch_range() from the
> > driver.
>
> We may as well stick prefetch_range() in prefetch.h.
>
> And Matt's patch series is not a thing I want to take on board at present,
> so let's stick with the straight scalability patch for now.
Sigh, I'll trim it back to some bits I think are critical.
> I moved the prefetch_range() call to outside the spinlock. Does that make
> sense?
I don't think that's actually a win. If there's contention, threads
racing to the lock will grab the same cache lines and all but one
thread's cache will end up invalidated by the time the lock is
released.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2004-03-26 4:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040325141923.7080c6f0.akpm@osdl.org>
2004-03-25 22:47 ` Fw: potential /dev/urandom scalability improvement Matt Mackall
2004-03-26 1:45 ` David Mosberger
2004-03-26 2:00 ` Andrew Morton
2004-03-26 2:10 ` David Mosberger
2004-03-26 4:07 ` Matt Mackall [this message]
2004-03-26 4:19 ` Matt Mackall
2004-03-26 4:51 ` David Mosberger
2004-03-26 5:15 ` Matt Mackall
2004-03-26 5:24 ` David Mosberger
2004-03-26 11:06 ` Dave Jones
2004-03-26 18:08 ` David Mosberger
2004-03-26 18:23 ` Dave Jones
2004-03-26 21:31 ` David Mosberger
2004-03-26 18:49 ` Andrew Morton
2004-03-26 20:25 ` David Mosberger
2004-03-26 20:33 ` Andrew Morton
2004-03-26 20:45 ` Arjan van de Ven
2004-03-26 21:17 ` Andrew Morton
2004-03-27 7:44 ` Arjan van de Ven
2004-03-26 21:12 ` David Mosberger
[not found] <1DLZM-8aK-67@gated-at.bofh.it>
[not found] ` <1DLZM-8aK-65@gated-at.bofh.it>
[not found] ` <1DOE1-20o-17@gated-at.bofh.it>
[not found] ` <1DOXn-2k7-5@gated-at.bofh.it>
[not found] ` <1DXxI-Z7-39@gated-at.bofh.it>
[not found] ` <1E467-6KK-17@gated-at.bofh.it>
[not found] ` <1E4IT-7f3-21@gated-at.bofh.it>
2004-03-27 1:29 ` Andi Kleen
2004-03-27 15:48 ` Matt Mackall
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=20040326040710.GF8366@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.