From: Andrew Morton <akpm@osdl.org>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, davej@redhat.com, mpm@selenic.com,
linux-kernel@vger.kernel.org
Subject: Re: Fw: potential /dev/urandom scalability improvement
Date: Fri, 26 Mar 2004 12:33:03 -0800 [thread overview]
Message-ID: <20040326123303.7a775b02.akpm@osdl.org> (raw)
In-Reply-To: <16484.37279.839961.375027@napali.hpl.hp.com>
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> >>>>> On Fri, 26 Mar 2004 10:49:04 -0800, Andrew Morton <akpm@osdl.org> said:
>
> Andrew> But the start address which is fed into prefetch_range() may
> Andrew> not be cacheline-aligned. So if appropriately abused, a
> Andrew> prefetch_range() could wander off the end of the user's
> Andrew> buffer and into a new page.
>
> Andrew> I think this gets it right, but I probably screwed something
> Andrew> up.
>
> Please, let's not make this more complicated than it is. The
> cacheline alignment doesn't matter at all. Provided prefetch_range()
> is given a range of guaranteed to be valid memory, then it will be
> fine. It never touches anything outside the specified range.
If someone does, say,
prefetch_range(some_pointer, sizeof(*some_pointer));
then it is possible that prefetch_range() could
a) execute a prefetch at addresses which are not PREFETCH_STRIDE-aligned
and, as a consequence,
b) prefetch data from the next page, outside the range of the user's
(addr,len).
next prev parent reply other threads:[~2004-03-26 20:34 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
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 [this message]
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=20040326123303.7a775b02.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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