From: Arjan van de Ven <arjanv@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: memset (was: Redundant memset in AIO read_events)
Date: Thu, 10 Jul 2003 10:33:17 +0000 [thread overview]
Message-ID: <20030710103317.D21655@devserv.devel.redhat.com> (raw)
In-Reply-To: <p73smpepte1.fsf@oldwotan.suse.de>; from ak@suse.de on Thu, Jul 10, 2003 at 12:29:10PM +0200
On Thu, Jul 10, 2003 at 12:29:10PM +0200, Andi Kleen wrote:
> The problem is that the instruction that avoid write-allocate usually also force
> the result out of cache.
that's for the current implementation; rep stosl may get the WA-avoiding
behavior sometime without the negative cache effects.. someday maybe.
next prev parent reply other threads:[~2003-07-10 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030710100417.83333.qmail@web11801.mail.yahoo.com.suse.lists.linux.kernel>
[not found] ` <1057832361.5817.2.camel@laptop.fenrus.com.suse.lists.linux.kernel>
2003-07-10 10:29 ` memset (was: Redundant memset in AIO read_events) Andi Kleen
2003-07-10 10:33 ` Arjan van de Ven [this message]
2003-07-10 10:04 Etienne Lorrain
2003-07-10 10:19 ` Arjan van de Ven
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=20030710103317.D21655@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=ak@suse.de \
--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