From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Xin Tong <xerox.time.tech@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: oostore on x86
Date: Mon, 9 Apr 2012 10:37:45 +0100 [thread overview]
Message-ID: <20120409103745.487fa6f1@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120408232728.GA29407@redhat.com>
> I've suggested just removing that code in the past a few times.
> Even if it does still work, anyone complaining about performance loss
> of a modern kernel on something of that era can't be taken seriously.
I'm not sure removing it makes sense given what a tiny spec of code is
involved. Also in practice most of the same bits are actually used with
different fencing operators on PPro for errata and on PIII and higher for
temporal stores. Of the tree tiny changes it causes two are identical to
PPro...
Alan
prev parent reply other threads:[~2012-04-09 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 19:48 Xin Tong
2012-04-08 21:49 ` H. Peter Anvin
2012-04-08 23:27 ` Dave Jones
2012-04-09 2:15 ` Xin Tong
2012-04-09 9:43 ` Alan Cox
2012-04-09 9:37 ` Alan Cox [this message]
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=20120409103745.487fa6f1@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xerox.time.tech@gmail.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
all inboxes | Powered by JetHome®