From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, akpm@digeo.com, taka@valinux.co.jp,
alan@lxorguk.ukuu.org.uk, neilb@cse.unsw.edu.au,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: [PATCH] zerocopy NFS for 2.5.36
Date: Fri, 20 Sep 2002 04:28:19 +0200 [thread overview]
Message-ID: <20020920042819.A1289@wotan.suse.de> (raw)
In-Reply-To: <20020919.190154.57630807.davem@redhat.com>
On Thu, Sep 19, 2002 at 07:01:54PM -0700, David S. Miller wrote:
> From: Andi Kleen <ak@suse.de>
> Date: Fri, 20 Sep 2002 04:06:19 +0200
>
> > See "montdq/movnti", the latter of which even works on register
> > registers. Ben LaHaise pointed this out to me earlier today.
>
> The issue is that you really want to do prefetching in these loops
> (waiting for the hardware prefetch is too slow because it needs several
> cache misses to trigger) so for cache hints on reading only prefetch
> instructions are interesting.
>
> I'm talking about using this to bypass the cache on the stores.
> The prefetches are a seperate issue and I agree with you on that.
I was talking generally. You cannot really use these instructions on Athlon,
because they're microcoded and slow or do not exist. On Athlon it needs
3dnow write combining functions (adding FPU overhead so may not be worth
it). On P3/P4 you can use movnti/movntdq yes.
Just doing it for reads is more tricky/dubious.
-Andi
next prev parent reply other threads:[~2002-09-20 2:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D89176B.40FFD09B@digeo.com.suse.lists.linux.kernel>
[not found] ` <20020919.221513.28808421.taka@valinux.co.jp.suse.lists.linux.kernel>
[not found] ` <3D8A36A5.846D806@digeo.com.suse.lists.linux.kernel>
2002-09-20 1:00 ` Re: [PATCH] zerocopy NFS for 2.5.36 Andi Kleen
2002-09-20 1:00 ` [NFS] " Andi Kleen
2002-09-20 1:09 ` Andrew Morton
2002-09-20 1:09 ` [NFS] " Andrew Morton
2002-09-20 1:23 ` Andi Kleen
2002-09-20 1:23 ` [NFS] " Andi Kleen
2002-09-20 1:27 ` David S. Miller
2002-09-20 2:06 ` Andi Kleen
2002-09-20 2:01 ` David S. Miller
2002-09-20 2:28 ` Andi Kleen [this message]
2002-09-20 2:20 ` David S. Miller
2002-09-20 2:35 ` Andi Kleen
2002-10-16 14:04 Lever, Charles
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 5:50 Neil Brown
2002-10-14 12:01 ` Hirokazu Takahashi
2002-10-16 3:44 ` Neil Brown
2002-10-16 4:31 ` David S. Miller
2002-10-17 2:03 ` [NFS] " Andrew Theurer
2002-10-17 2:31 ` Hirokazu Takahashi
2002-10-17 13:16 ` Andrew Theurer
2002-10-17 13:26 ` Hirokazu Takahashi
2002-10-17 14:10 ` Andrew Theurer
2002-10-17 16:26 ` Hirokazu Takahashi
2002-10-18 5:38 ` Trond Myklebust
2002-10-18 7:19 ` Hirokazu Takahashi
2002-10-18 15:12 ` Andrew Theurer
2002-10-19 20:34 ` Hirokazu Takahashi
2002-10-22 21:16 ` Andrew Theurer
2002-10-23 9:29 ` Hirokazu Takahashi
2002-10-24 15:32 ` Andrew Theurer
2002-09-19 2:00 Lever, Charles
2002-09-18 23:00 David S. Miller
2002-09-18 23:54 ` Alan Cox
2002-09-19 0:16 ` Andrew Morton
2002-09-19 13:15 ` [NFS] " Hirokazu Takahashi
2002-09-19 20:42 ` Andrew Morton
2002-09-19 21:12 ` David S. Miller
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=20020920042819.A1289@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=taka@valinux.co.jp \
/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.