From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Neil Romig" <neil@romig.demon.co.uk>,
linux-kernel@vger.kernel.org, hyoshiok@miraclelinux.com,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: File corruption when using kernels 2.6.18+
Date: Wed, 3 Oct 2007 22:35:24 +0300 [thread overview]
Message-ID: <84144f020710031235r29986ceaj3260e8271eee6ddb@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0710031209450.3579@woody.linux-foundation.org>
Hi Linus,
On 10/3/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> I would bet that the reason the intel-optimized memcpy triggers this is
> that the non-temporal stores just means that you go out directly on the
> bus, and it probably just shows a weakness in the chipset or bus that
> doesn't show with the normal cacheline accesses.
But that should show up with memtest too, no?
Pekka
next prev parent reply other threads:[~2007-10-03 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 15:40 Neil Romig
2007-09-30 16:29 ` Pekka Enberg
2007-10-02 21:05 ` Neil Romig
2007-10-03 5:18 ` Pekka Enberg
2007-10-03 18:42 ` Neil Romig
2007-10-03 18:48 ` Pekka Enberg
2007-10-03 19:22 ` Linus Torvalds
2007-10-03 19:35 ` Pekka Enberg [this message]
2007-10-03 19:54 ` Linus Torvalds
2007-10-04 1:11 ` Hiro Yoshioka
2007-10-03 20:30 ` Alan Cox
2007-10-04 18:34 ` Neil Romig
2007-10-02 22:30 ` Chuck Ebbert
[not found] <fa.VCoGTwbB+qeNlkBJ24MiuXcGSRA@ifi.uio.no>
[not found] ` <fa.R+FhT6IGmV/dDweUt/MdSeA5YbQ@ifi.uio.no>
[not found] ` <fa.7MxTIt/ik0uRFN/lMWUasYV/JyE@ifi.uio.no>
[not found] ` <fa.YJ4uCPzXT5TQElSosyz98cpuMSc@ifi.uio.no>
[not found] ` <fa.Tp9UUX9EYprQyLg0shgH1YG9DDM@ifi.uio.no>
[not found] ` <fa.PzpJEEoLXfC+eOQZjTWjdf9vdnE@ifi.uio.no>
2007-10-04 2:59 ` Robert Hancock
2007-10-04 3:39 ` Linus Torvalds
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=84144f020710031235r29986ceaj3260e8271eee6ddb@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=hyoshiok@miraclelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@romig.demon.co.uk \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®